Hacker News Reader

Comment by nfm | Hacker News Reader

You'll need to add 'therubyracer' (or another javascript interpreter) to your Gemfile. It requires python and a C++ compiler to compile its binaries.

If you're on Heroku, you may need 'therubyracer-heroku' instead - there are compilation issues. Hopefully this will be fixed soon.

View on HN

This needs the V8 stuff compiled and installed. And then I'm running yet more code on my production servers to deploy. And this code compiles the CoffeeScript to JS, and this will be the very first place that this code will have actually been tested in this configuration.

This deployment scares me a lot -- partly because I haven't yet made it work in an RC build, and mainly because it adds more moving parts to my production servers.

You do not need to use CoffeeScript in Rails 3.1, it is merely the default option. Just delete the "gem 'coffeescript'" line in your Gemfile and just use regular js.

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.

Node.js isn't required. You can use any of the seven javascript runtimes that the ExecJS gem supports.

https://github.com/sstephenson/execjs

:s/Node.js/Not Ruby

I 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.

Reply on news.ycombinator.com