News for hackers. Stuff that matters.
Re:Node v0.12.0 (Stable) by wereHamster on Friday February 06, 2015 @05:38PM (#9012031)
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.

Re:Node v0.12.0 (Stable) by domenicd on Friday February 06, 2015 @05:40PM (#9012050)
Nope. They're using V8 3.28.73 and libuv 1.0.2, both of which are abandoned by their maintainers.
Re:Node v0.12.0 (Stable) by maxogden on Friday February 06, 2015 @05:44PM (#9012081)
iojs 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
Re:Node v0.12.0 (Stable) by Kiro on Saturday February 07, 2015 @12:59AM (#9013233)
> I'm sharing part of my code between server and client

How? And why is it a problem with node but not iojss?

Re:Node v0.12.0 (Stable) by maratd on Saturday February 07, 2015 @03:31AM (#9013473)
You 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.

Re:Node v0.12.0 (Stable) by wereHamster on Saturday February 07, 2015 @06:15AM (#9013676)
Because 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.