On 10-06-2014 14:59, Steve Klabnik wrote:
Right, I guess I've had enough troubles with the 'builtin' JS runtimes in Mac/Windows that I always end up installing Node anyway. :/
This is not just a matter of preferences. When I was investigating why compiling my CoffeeScript files was so slow with Sprockets when compared to the "coffee" command I realized the overhead of spawning a new process for every CS file was the culprit.
Replacing Node.js with therubyracer gem saved us 15s when compiling the assets. Running "time rake assets:clobber assets:precompile" takes about 15s for our application. If I use EXECJS_RUNTIME=Node it takes about 30s.
I don't have any experience on Mac or Windows though. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/rubyonrails-core. For more options, visit https://groups.google.com/d/optout.
