NodeJS is currently tightly coupled to Google's V8 engine. V8 was not designed as a server-side engine, but as a browser-based engine. Furthermore, V8 was designed squarely to run in Chrome's multi-process model. As much as I think V8 is a brilliant piece of engineering, it's software that was not designed to run on a server.
More to the point, it's really up to Google to work with the community to make V8 work on the server-side. Sometimes Google is responsive, but sometimes it might not. It varies as it depends how fixing a bug or applying a patch may align with Google's product roadmap and plans. I don't know Google's plans, and I suspect most NodeJS committers don't know either.
Maybe for some folks this might not seem like a big problem. And probably, if you are running a site with a few thousand daily page views, it might actually not be a big deal. But to Yahoo!, and to others, it's a big deal and we believe this is fundamental to the success of the NodeJS project.
Google may invest on supporting V8 on the server-side, just like the Mozilla folks do. Or somebody else might invest and ensure V8 is rock-solid on the server and Google may merge the patches nicely. Or maybe not, and the community may need to fork V8. Or something else ... Nobody really knows.
Either way, it's time for the NodeJS community to realise there is a roadblock and discuss it openly.
blog comments powered by Disqus