Live data from Hacker News

Node v0.12.0 (Stable)

blog.nodejs.org

1–10 of 81 posts

Re: Node v0.12.0 (Stable)

#2
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)

#3

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.

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)

#4

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.

[deleted]

Re: Node v0.12.0 (Stable)

#6

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.

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)

#7

As a casual node user, I'd love to better understand how this release compares to io.js. Are they diverging more? Is node playing catch-up?

Node inspector should now work properly like it does on iojs (https://github.com/joyent/node/issues/7102) but this still isn't a stable v8, according to the v8 maintainers.

Re: Node v0.12.0 (Stable)

#10
post #8

Meh, too late. io.js is the standard now.

Yep, io.js v1.1 works really fine and i switched too.

My experience has been that just about every module that uses native code (there are more than you think) doesn't work in IO.js because of the changes to the V8 apis. So until all of those are updated to work with both I'll have to stick to Node.
Post reply on HN