tag:blogger.com,1999:blog-4107046333918914156.post5959912054629552469..comments2023-10-02T13:22:21.060+05:30Comments on RoR Guide & Solutions: 'ExecJS::RuntimeUnavailable' error after creating new Rails4 applicationRitesh Kumarhttp://www.blogger.com/profile/15542267935254656934noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-4107046333918914156.post-41593459566225243652013-09-09T09:05:10.184+05:302013-09-09T09:05:10.184+05:30Thanks Glauco for prompt clarification.Thanks Glauco for prompt clarification.Ritesh Kumarhttps://www.blogger.com/profile/15542267935254656934noreply@blogger.comtag:blogger.com,1999:blog-4107046333918914156.post-84101067217681811572013-09-09T01:42:59.174+05:302013-09-09T01:42:59.174+05:30As I understand it, you need a server-side javascr...As I understand it, you need a server-side javascript runtime. Installing therubyracer gem as you did is an option, but not the only one. I've seen some benchmarks claiming it's faster to use nodejs in the server, for example. <br /><br />The difference is that therubyracer can be installed via bundler as a gem, while nodejs has to be installed with whatever package manager your distro uses (pacman, apt-get, whatever). Also with therubyracer gem you can easily deploy to your staging/production machines using capistrano, and the "bundle install" step in the deployment will install the gem; on the other hand with nodejs or other non-gem solutions you have to install them by hand in each machine. <br /><br />Unless you use puppet or something like that, I suppose; I'm not proficient with it so I cannot comment.Alfredo Amatriainhttps://www.blogger.com/profile/03801608106391615049noreply@blogger.com