I understand your frustration -- you may not think so, but I get it. That being said, the other points I made were in support of the answer I pose to the question: Rails is growing up. The changes we've seen aren't just change for change's sake. They're changes that continue Rails' evolution by identifying pain points and presenting a default solution to them, one that can be opted out of if desired. This is not new for Rails, but it seems like every time we turn around, people are acting surprised.
They're changes that continue Rails' evolution by identifying pain points and presenting a default solution to them, one that can be opted out of if desired
-------------------------
You're thinking "Why can't they just opt out of this and let us have our fun" and we're thinking "why are they forcing this on everybody".
Its kind of how you get a windows box and it has all this crap on it by default ... you can go uninstall or turn stuff off, but its fricking annoying as heck.
Some things should be the way things are done in rails, bundler, the new ActiveRecord queries. yes
Some of this other stuff, not so much ... you should have to explicitly turn it on not turn it off, and then if we're seeing wide adoption then we can make it part of the core.
What is wrong with that approach?
one that can be opted out of if desired. This is not new for Rails, but it seems like every time we turn around, people are acting surprised.
---------------
Don't make people opt out of stuff especially on things that might not be so core to rails ... Opting out is annoying ... its much better to go "Wow, I didn't know that was there" than "crap ... I have to turn this stuff off now". It gets on people's nerves, the fact that you're not seeing that despite confessing that people complain each time it happens suggests a certain amount of tone deafness.
I could be wrong, but I think its worth re-evaluating.
