What Blocks Ruby and Python from Getting to JavaScript V8 Speed?

Re:What Blocks Ruby and Python from Getting to JavaScript V8... by bkeroack on Friday January 16, 2015 @05:54PM (#8902295)

When Ruby or Python is too slow you can switch to something else. When JavaScript is too slow you have to either pay someone to make your code faster or pay someone to make the browser faster.

[ Parent | on HN ]

Re:What Blocks Ruby and Python from Getting to JavaScript V8... by iamvfl on Friday January 16, 2015 @11:47PM (#8903441)

Not all JavaScript runs in the browser

[ Parent | on HN ]

Re:What Blocks Ruby and Python from Getting to JavaScript V8... by _delirium on Saturday January 17, 2015 @05:28AM (#8904032)

It mostly did before V8 was created. A few people ran JS outside the browser using Mozilla's Rhino, but it wasn't very common. Nodejs probably was the first widely adopted platform for non-browser JS, and it was built on V8 after V8 already existed. So I believe historically server-side JS did not drive JS performance.

[ Parent | on HN ]

Re:What Blocks Ruby and Python from Getting to JavaScript V8... by SixSigma on Saturday January 17, 2015 @12:21PM (#8904821)

It should be mentioned that Microsoft has had server side Javascript (well, Jscript) running on IIS since 1997. I used to write data driven websites in it.

http://en.wikipedia.org/wiki/JScript

[ Parent | on HN ]

Re:What Blocks Ruby and Python from Getting to JavaScript V8... by ksherlock on Saturday January 17, 2015 @07:44PM (#8906158)

and Windows Script Host (wscript/cscript).

[ Parent | on HN ]