It is profoundly sad how Rails has institutionalized a "nobody cares" attitude toward performance.https://twitter.com/samsaffron/status/1002446941156884480 …
-
-
This is the first time I am bringing up my issues with the doctrine, nobody owes me anything, and I shut up for many years about my issues with it. But yes I think it is fair to say that the doctrine totally justifies making Rails 10% slower provided developers are 100% happier
-
Probably. I don't really care about what the doctrine does or doesn't say, personally. It doesn't prioritize what I do or don't work on.
- 3 more replies
New conversation -
-
-
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?
- 16 more replies
New conversation -
-
-
I honestly don't feel AR can be fixed at this point, due to the deep cultural issues of "developer happiness > everything else". It's better to invest in building alternative (but compatible) paths, kind of like Merb did back in the day.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
the doctrine does not say "secondary"; performance is not even mentioned. What it does say is that developer happiness is, by far, the most important factor and the only one that matters.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
also, for the record ... Sam Saffron is not Jeff Atwood. I have my opinions and Jeff has his. My goal was to help present a proper picture about existing problems. Jeff has heard about these issues for many years and is frustrated.
-
Wasn't confusing you two, don't worry. :)
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.