Thank you, everyone. This was an issue only in my Fedora laptop. In my OSX, not a problem at all. I knew all along that installing therubyracer or nodejs would fix this, I just didn't know the "why" since I thought these weren't javascript interpreters; that they themselves were written in javascript that required a javascript interpreter.
That said, I installed therubyracer and I did see libv8 being installed along with it. This I believe is the javascript interpreter so it now makes sense and I understand that it is used only for compiling the assets in asset pipeline. Thanks again for everyone's input. p On Sunday, April 7, 2013 3:35:04 AM UTC-7, Frederick Cheung wrote: > > > > On Friday, April 5, 2013 7:01:50 PM UTC+1, Peter wrote: >> >> Thanks for replying, Frederick. So help me understand this: >> javascript-runtime is actually the javascript interpreter. Right? But what >> is odd is when I install node-js this solves my problem. And I thought >> node-js *was* written in javascript. Therefore, it itself requires an >> interpreter. Did I get this wrong? So how does installing node-js, a >> javascript script, solve the problem of not having a javascript interpreter >> to begin with? >> >> node-js is both both google V8 javascript engine plus some libraries > (much as for example ruby is the ruby interpreter plus a bunch of standard > library stuff) > > Fred > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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]. To view this discussion on the web visit https://groups.google.com/d/msg/rubyonrails-talk/-/0fNqV41Nu98J. For more options, visit https://groups.google.com/groups/opt_out.
