Miss Dada  🏳️‍⚧️

"Performance is secondary to developer happiness" is not the same as "we actively don't care about performance". Rails is a project run by volunteers and has limited resources. Y'all are talking like we're actively just ignoring performance, vs having to prioritize our time.

There are also plenty of people, yourself included, who have spent sustained effort improving Rails performance. The false dichotomy is really destructive to both causes, and create gridlock between perspectives that gets nothing done.

What's the point of rhetoric that convinces folks who want to improve developer ergonomics that their goals are in conflict with performance? What do you think will happen over the long haul if performance-minded folks act like the tradeoff is zero-sum?

It's funny that you bring this up, because we want a Merb style outcome here and that's what we are working toward. I honestly don't feel AR can be fixed because of the deep seated cultural issues of "developer happiness > everything else"

If that's true about AR it should absolutely have been true about Glimmer. Developer friendly APIs are declarative enough to make under the hood changes with profound effects.

More developers should internalize the fact that performance actually matters... at *LEAST* equal to "developer happiness". If they did, we'd have made more progress by now, rather than having to drag people, kicking and screaming, across the goal line

Please stop generalizing every person who works on Rails as a homogenous group. You are putting words in our mouths that are not true.

It's also just actually true that sometimes performance is an ergonomics issue. @ryanflorence made this point very viscerally years ago to the Ember community in his React talk about how bad performance sometimes makes it hard to say "yes" to features.