Completely agree. However, instead of bundling one asset pipeline into rails that is "aggressive" like Sprockets about getting into everything, they should have said "here's a connector" where you can attach the "asset pipeline" of your choice and let the community create the tools it needs for different scenarios, such as one asset pipeline for thin clients and another for think clients. Or separate asset pipelines for sass/css and coffeescript/javascript.
Bundling a default that doesn't play well with lots of the client-side innovations hurts rails more than helps.
The asset pipeline as it is currently designed is monolithic and an all or nothing approach.
I got downvoted into oblivion (deservedly so) because of my snark. But this is essentially the point I was trying to make. Rails is good at ruby. It was never good at javascript. Remember rjs? Remember inlining ajax handlers?
Now we have default coffee script and sass file _per_ view. I know they mean well but javascript is its own beast! I really don't want to have to consciously disable all these things that are supposed to "be convenient" just because I know my way around javascript enough to not co-mangle it in with ruby.
Bundling a default that doesn't play well with lots of the client-side innovations hurts rails more than helps.
The asset pipeline as it is currently designed is monolithic and an all or nothing approach.