Rails 3.1 Adopts CoffeeScript, jQuery, Sass and.. Controversy

Well, bad news guys:<p><a href="http://doihavetousecoffeescriptinrails.com/" rel="nofollow">http://doihavetousecoffeescriptinrails.com/</a>

I don't see why this should be controversial, it's so easy to switch to Haml, Sass or jQuery when you need/want to. The defaults are there to get the uninitiated off the ground as quickly as possible, and is in keeping with the 'rails way'.<p>I, on the other hand, have my 'own way', and rails doesn't in any way prevent me from implementing that when I start a new rails project.

How will this be integrated? Does this just mean when I generate a rails project, I'll see:<p><pre><code> gem 'haml' gem 'coffee' </code></pre> in my Gemfile? That's cool, I just hope this stuff isn't vendored.

While I don't agree with this change, I have to hand it to DHH -- he brings "opinionated" to breathtaking heights :)<p>And he's right -- these kind of changes may be controversial, but Rails was never about being mainstream / safe / conservative. Rails was always about being productive, and in that context taking risks is good -- which is the reason for the dozens of Rails-clones written in dozens of languages.

Why not haml? Was there a discussion about this?

Who cares? How much longer is this going to drag on? It doesn't force you to use CoffeeScript, you can easily continue to write JavaScript or Sass with no detrimental effects. If I understand correctly, it only changes the templates created.