I remember a time ...

Remember that Steve Jobs appointed his COO Tim Cook to take over Apple. Not Ives or Cue or Federighi. I've always seen this as an acknowledgment that without Jobs the company would not be able to innovate in the same way.

Having acknowledged that, Apple shifted to the value extraction phase of its business lifecycle.

It sucks.

It like when your favorite band starts selling out, but as publicly traded company, I am not sure it is avoidable.

> Not Ives or Cue or Federighi.

It’s “Ive” and Federighi wasn’t a candidate in 2011.

Also, how you think someone is going to work out and how they actually work out is still worth commenting on. Not every CEO would have extracted value in the same way. You can prioritize extracting value by making customers super happy so they buy more. That’s what the article is about.

i saw an interview with ives recently. he wasnt even close to being qualified for that job. it wasnt even an option

I like this idea!

Having SSH in the name helps developers quickly understand the problem domain it improves upon.

That is a rather dismissive attitude that could cause you to overlook some great technologies.

Or it's a quick heuristic to filter out misaligned philosophies.

I've been using apache echarts for a while. It is excellent. As you dig deep, some of the examples and libraries are in Chinese, which can be challenging.

The only real drawback that I've discovered is that it uses canvas to generate the charts. So, when you UI changes to dark mode, you need to reload your charts to update the color scheme ... which in the grand scheme of things is really minor.

Well, taste for a Global Interpreter Lock, at least.

Same. Texas.

A bit off topic, but whenever Rails and templating get brought up, I have to plug my absolute favorite project out there: Phlex https://beta.phlex.fun/. It's like ViewComponents, but swap out the ERB for pure Ruby. It has been a joy to develop with.

With the addition of Phlex::Kit, it has made building out a component library pretty easy too. RubyUI https://github.com/ruby-ui/ruby_ui does a great job of showing off how to do this.

Those kind of things used to be a lose lose proposition back at the time of haml (?) and all the yaml like templating languages. That was more than 10 years ago. The reason was that any designer that could actually do html was able to write an erb page, maybe except loops and logic, but they could understand them if a developer added them into the page later. On the other side with one of those languages, and more with phlex, only a developer could write the views so we were back to the 90s with photoshop layouts.

Furthermore your can't copy and paste examples. Think about Bootstrap components. You have to really write everything from scratch.

https://www.phlexing.fun/ We have this for that. :)

Agreed. The whole idea of writing html from scratch using special tags in the code makes no sense to me. It basically destroys the separation between code and design/templates.

Funnily enough I write most of my view components without a template these days, unless there's a load of markup.

I keep meaning to take a look at Phlex.

It really depends on the use case. Right?

Sure, if you are building an enterprise application, this likely doesn't make any sense.

But, if you are building something for a consumer audience. Or if you are trying to differentiate yourself by building something beautiful. Then maybe wrap these 100 lines of code in a very specific class name (.fancyGlassFrostedGlass) and call it day?

This is the first site I've run in to that uses neumorphic design. Love the aesthetic -- just never seen in it the wild before.

CRED had it in their app for a while, their library is open source

https://github.com/CRED-CLUB/synth-android