I'm sorry that this comment got downvoted because I actually think this is a valid point even if I'm about to offer my perspective on why it shouldn't be a concern. We shouldn't be so thin-skinned.
Nothing you weren't expecting, but: like many libraries which shipped with Rails, you can easily turn it off with a single comment character and never have to think about it again. In this sense, it's a tempest in a teapot. I never got excited about CoffeeScript, so I just commented it out.
Big picture, Rails is often mistaken for a product but it is quite literally just a set of useful abstractions from Basecamp that hit critical mass when Basecamp launched. If other people find it useful, great - but that's never been the MO.
Now, obviously Rails also has a life of its' own, and that's where the idea of convention over configuation kicks in. Basically, DHH has strongly-held opinions about the way things should be done to maximize the experience of building. The new multi-db support is another example of something that people have been building their own versions of since forever; by offering an opinionated generalized take on how the experts would do it, we all benefit from not having to reinvent the wheel.
I honestly believe that this is why Rails is both successful and enduring. I love seeing all of the comments from people who were seduced by SPAs and are finding their way back to SSR Rails. The productivity and ease of hiring is just unparalleled, and commenting out ActiveText or whatever else you don't need takes away none of that.
Nothing you weren't expecting, but: like many libraries which shipped with Rails, you can easily turn it off with a single comment character and never have to think about it again. In this sense, it's a tempest in a teapot. I never got excited about CoffeeScript, so I just commented it out.
Big picture, Rails is often mistaken for a product but it is quite literally just a set of useful abstractions from Basecamp that hit critical mass when Basecamp launched. If other people find it useful, great - but that's never been the MO.
Now, obviously Rails also has a life of its' own, and that's where the idea of convention over configuation kicks in. Basically, DHH has strongly-held opinions about the way things should be done to maximize the experience of building. The new multi-db support is another example of something that people have been building their own versions of since forever; by offering an opinionated generalized take on how the experts would do it, we all benefit from not having to reinvent the wheel.
I honestly believe that this is why Rails is both successful and enduring. I love seeing all of the comments from people who were seduced by SPAs and are finding their way back to SSR Rails. The productivity and ease of hiring is just unparalleled, and commenting out ActiveText or whatever else you don't need takes away none of that.