3 ms·
No mention which version of V8 they use. Did they sync with what Chrome is using nowadays? Anyways, I've already switched to iojs. I'm sharing part of my code
by wereHamster 12y ago
No mention which version of V8 they use. Did they sync with what Chrome is using nowadays?
Anyways, I've already switched to iojs. I'm sharing part of my code between server and client and it has become increasingly painful to work around the lack of progress on the nodejs side of the network.
- domenicd 12y agoNope. They're using V8 3.28.73 and libuv 1.0.2, both of which are abandoned by their maintainers.
- deleted 12y ago[deleted]
- maxogden 12y agoiojs 1.1.0 V8 version 4.1.0.14 (current). nodejs 0.12 V8 version: 3.28.73 (>6 months old). More info here: https://iojs.org/es6.html https://iojs.org/es6.html
- Kiro 12y ago> I'm sharing part of my code between server and client How? And why is it a problem with node but not iojss?
- maratd 12y agoYou can easily use the same framework both on the server and client, especially a general purpose one. Makes life easier. io.js uses the current version of V8. node uses an outdated one. Makes life easier if your code is being executed in the same engine, with the same version. Everything that works in one, works on the other.
- deleted 12y ago[deleted]
- wereHamster 12y agoBecause Chrome and Firefox now provide many ES6 features which are missing from nodejs. But iojs tracks the latest stable v8 so it is feature-wise at the same level as Chrome.