I can't say much about Rails, but I will say that after doing a CoffeeScript, Backbone, and require.js with clientside compilation project -- debugging is pain and tears. Even though Chrome supports source maps, CoffeeScript doesn't, and the error messages raised by require.js are of the "you fucking peon" variety referred to in the article.
I like CoffeeScript and AMD, but they aren't ready to be in the same room together. Hopefully, jrburke's almond will let me build a serverside compilation strategy that isn't awful to debug.
On the other hand, Backbone kicks ass, and I wrote a DOM-twiddling Knockout.js inspired data binder called _outback.js_ to make it better. It's up on github (politician/outback) if anyone's interested.
I like CoffeeScript and AMD, but they aren't ready to be in the same room together. Hopefully, jrburke's almond will let me build a serverside compilation strategy that isn't awful to debug.
On the other hand, Backbone kicks ass, and I wrote a DOM-twiddling Knockout.js inspired data binder called _outback.js_ to make it better. It's up on github (politician/outback) if anyone's interested.