3 ms·
I was hoping (sadly) that based on the name, this meant there was a port of node.js to spidermonkey by the Mozilla team. Other posters have mentioned this as w
by binarycrusader 12y ago
I was hoping (sadly) that based on the name, this meant there was a port of node.js to spidermonkey by the Mozilla team. Other posters have mentioned this as well.
This is sort of a "lazy web" request, but does anyone know why node.js needs v8 specifically? Would it really be that hard to support node.js on spidermonkey?
- mbrubeck 12y agoThere was a "Spidernode" project started a while ago: http://zpao.com/posts/about-that-hybrid-v8monkey-engine/ http://zpao.com/posts/about-that-hybrid-v8monkey-engine/ I believe it fizzled out partly due to lack of contributor time and partly because the mainstream Node maintainers were wary of fragmenting the Node.js ecosystem/community.
- cpeterso 12y agoIn the name of competition and architectural flexibility, perhaps the io.js team will be more receptive. :) AFAIK, though, V8 is so tightly integrated into Node core that a third-party library, NaN ("Native Abstractions for Node.js"), was created to improve API compatibility for Node binary addons: https://github.com/rvagg/nan https://github.com/rvagg/nan