4 ms·
That's the problem though; Rails now depends on an implementation of a second programming language (coffeescript) that's only implemented inside another languag
by bonzoesc 15y ago
That's the problem though; Rails now depends on an implementation of a second programming language (coffeescript) that's only implemented inside another language environment (node.js) that changes quickly enough that many OSes don't have working packages for it.
Coffeescript is rad as hell, but making Rails depend on it by default without a really great way to install it seems foolish.
- chanks 15y agoNode.js isn't required. You can use any of the seven javascript runtimes that the ExecJS gem supports. https://github.com/sstephenson/execjs https://github.com/sstephenson/execjs
- ebiester 15y ago:s/Node.js/Not Ruby
- skidooer 15y agoI admittedly haven't spent much time with Rails 3.1, but isn't that what rake assets:precompile is for? Automatic compilation of coffee scripts is nice in development, but not overhead you want to add for production anyway.