Re:Temporary fork enables Node.js to optionally use the Chak...
by bsimpson on Wednesday May 13, 2015 @12:50AM
(#9536823)
Using @zpao's example, most Python developers use CPython and either don't know about PyPy or have never used it. As such, I'd expect most of the long-tail of Python libraries to have been written and tested against CPython.
That hasn't prevented PyPy, IronPython, JPython, etc. from existing/thriving.
Re:Temporary fork enables Node.js to optionally use the Chak...
by angersock on Tuesday May 12, 2015 @11:38PM
(#9536608)
Having a decent shim to code against instead of having to deal with the internal gooiness of different JS engines is actually very much preferred. By throwing a shim over the JS execution layer, they actually make the life of extension developers much easier.
I'm not sure exactly where I sit on this one. In many regards I think I like it, allowing developers to use the right engine for the right job, for example. Each engine has its own strengths and it may be that v8 isn't the engine for you / your workload. It's just this could hurt as much as it helps.