3 ms·

From what I understand, the "stability" argument, made by many for node.js, is a bit meaningless. Node.js uses an old V8 version ( Google doesn't support it an

From what I understand, the "stability" argument, made by many for node.js, is a bit meaningless. Node.js uses an old V8 version ( Google doesn't support it anymore, and they don't even apply security patches to it ) while io.js has the latest V8, plus all the security patches and bug fixes from the io.js codebase, that node.js does not have. Same story with libuv, the "main" library under the hood. ( most of this explained in this podcast http://devchat.tv/js-jabber/147-jsj-io-js-with-isaac-schleuter-and-mikeal-rogers http://devchat.tv/js-jabber/147-jsj-io-js-with-isaac-schleut... ) If older === more stable, then I guess you should use the oldest version in everything. Makes no sense.

falcolas 12y ago
Google offers support for v8 outside of Chrom(e|ium)? I can't find anywhere that Google lists what their supported versions of v8 are. Can you point me towards that list? More importantly, has Google shown genuine interest in supporting embedding v8? Their last blog post about this was in 2012. As for libuv, I would rather use a battle tested version, than stay on the bleeding edge. Threading is hard, and race conditions are rarely caught by tests. I'm happy to let others break their production and identify the regressions before I commit to it. Wanting to use proven software has no relation to using the "oldest" version. As software is used, bugs are found. The longer you wait to transition to using new features, the fewer bugs you will encounter when you make the transition. What's nonsensical about that?
- coderzach 12y ago
  Even "proven" software gets bug and security fixes. The version of v8 they're using doesn't. Therefore, unsupported.
dap 12y ago
The V8 question seems to come up a lot, but the V8 team only supports any branch for 6 weeks after it becomes stable for Chrome.[1] If this is your definition of supported, then if you plan to use any version of Node or io.js for more than 6 weeks, you'll wind up on an unsupported branch. [1] https://groups.google.com/d/msg/v8-users/UUyavs0KtwE/dhh4F8ciZwEJ https://groups.google.com/d/msg/v8-users/UUyavs0KtwE/dhh4F8c...

falcolas 12y ago

Google offers support for v8 outside of Chrom(e|ium)? I can't find anywhere that Google lists what their supported versions of v8 are. Can you point me towards that list? More importantly, has Google shown genuine interest in supporting embedding v8? Their last blog post about this was in 2012. As for libuv, I would rather use a battle tested version, than stay on the bleeding edge. Threading is hard, and race conditions are rarely caught by tests. I'm happy to let others break their production and identify the regressions before I commit to it. Wanting to use proven software has no relation to using the "oldest" version. As software is used, bugs are found. The longer you wait to transition to using new features, the fewer bugs you will encounter when you make the transition. What's nonsensical about that?

coderzach 12y ago
Even "proven" software gets bug and security fixes. The version of v8 they're using doesn't. Therefore, unsupported.

dap 12y ago

The V8 question seems to come up a lot, but the V8 team only supports any branch for 6 weeks after it becomes stable for Chrome.[1] If this is your definition of supported, then if you plan to use any version of Node or io.js for more than 6 weeks, you'll wind up on an unsupported branch. [1] https://groups.google.com/d/msg/v8-users/UUyavs0KtwE/dhh4F8ciZwEJ https://groups.google.com/d/msg/v8-users/UUyavs0KtwE/dhh4F8c...