Miss Dada  🏳️‍⚧️

This is a really bad take. @samsaffron has had access since March to the repository for an experiment I've been working on for a long while to fix exactly this. I've asked for help getting benchmark numbers for it on Discourse... I have no clue why it wasn't included here.

I will revise that to include numbers for the experiment repo, and the take that nobody cares about performance is not correct. However the current giant pain needs no additional libraries to get solved for PG it can be fixed in Ruby

The take that "developer happiness" is the only thing that matters, and that performance can be ignored, is absolutely enshrined in Rails culture.. and has been from day one.

It is fair to say that for me it is very disappointing that https://rubyonrails.org/doctrine/  says nothing about performance. Performance is not a priority for the doctrine. Consumers of Rails at scale have a very different take.

"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"