jxcore

The Node fork JXCore supports Chakra, SpiderMonkey and V8 right now. It's pretty fast, probably because it's based on a pre-0.12 node fork when node was known to be faster than it is presently. https://github.com/jxcore/jxcore

There is an actively maintained Spidermonkey port of Node.js called jxcore. It also supports an older version of V8 from the 0.10 branch. https://github.com/jxcore/jxcore

It is open source: https://github.com/jxcore/jxcore

is there any link from any of the jxcore pages to that year old page ? It even says that download Beta 2... What beta 2 is that? https://github.com/jxcore/jxcore is the place (as you and he already knows) we publicly give out the source codes. Even a new graduate can see what's been going on. Hey.. it's visible there is nothing to crack.

JXcore is fork of Node that supports either V8 or SpiderMonkey. I suspect neither the Node or io.js developers are interested because they don't want the extra maintenance costs of supporting more platforms and abstraction layers. However, decoupling your product's core from its third-party dependencies is usually a good idea. V8 API and ABI changes have been enough a problem that someone created the NaN library (Native Abstractions for Node.js) to help Node plugin maintainers. https://github.com/jxcore/jxcore https://github.com/rvagg/nan

// Suites of benchmarks consist of a name and the set of benchmarks in // addition to the reference timing that the final score will be based // on. This way, all scores are relative to a reference run and higher // scores implies better performance. https://github.com/Nubisa/jxdocs/blob/master/benchmarks/core... For complete clarity, see also the lines https://github.com/Nubisa/jxdocs/blob/master/benchmarks/core... The score is (arbitrary reference constant) / (geometric mean of runtime). Bad performance ==> longer runtime ==> lower scores.

Wait, I'm confused. From the following line: https://github.com/Nubisa/jxdocs/blob/master/benchmarks/core... Doesn't this line calculate the amount of time it takes to compute a single task? (elapsed time / number of runs = time per run) Doesn't this mean that JXcore is actually faster, since the number would be smaller with more runs?

Looking at the linked benchmark file appears to bear out this claim: https://github.com/Nubisa/jxdocs/blob/master/benchmarks/core... It appears that the reported numbers for benchmark X are _the # of times that X can be run before one second elapses_, so parent comment is correct and the premise of the blogpost (that the new node.js version with V8 has worse performance than the earlier version / the private fork has better performance than the new version and slightly worse performance than the old) is contradicted by the evidence presented. Not a good way to look competent, posting something like this. Countdown until edit or takedown...