Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Node v0.12.0 (Stable)

blog.nodejs.org

Post reply on HN
Print view View original

41–50 of 81 posts

Re: Node v0.12.0 (Stable)

#41

Post by hyperpape »

tracker1 wrote: post #36
bshimmin wrote: post #19

Earlier quoted context omitted.

Not sure if this is a joke, but assuming it's not - it's the standard now, and it's been out for... 2 whole months?!

It's based on node.js from just before the 0.12 stable release. The v8 and libuv base libraries and other pieces have been updated. It's not like they started io.js from scratch. It's that most of the core developers have moved on to io.js at this point. Barring a merge back into node.js (which could still happen), I don't see myself going back for new projects.

That's a fine attitude, but nothing about it justifies talk of "standard".

Re: Node v0.12.0 (Stable)

#42

Post by LukeB_UK »

bcantrill wrote: post #16

Several have asked about node.js in contrast to io.js. It's fair to say that the emphasis of node.js at this point is on stability (including API stability, production debuggability/observability, etc.) and performance -- in that order. It definitely takes longer to release software when operating under these constraints; as the team writes in the linked blog entry: We are also pleased to report that this release of…

A little disingenuous to say the tests pass when they landed this PR: https://github.com/joyent/node/pull/8689

Edit: Also, you should probably mention that you work for Joyent.

Re: Node v0.12.0 (Stable)

#43

Post by LukeB_UK »

bcantrill wrote: post #28
nailer wrote: post #26

Earlier quoted context omitted.

How does the stability concern gel with a unmaintained v8?

The idea of a "maintained" V8 is a bit of a myth -- there really isn't such a thing. Mostly, when V8 breaks node.js (e.g., by changing/eliminating a C++ API or by implicitly or explicitly breaking debugging support), node.js has to change. In that regard, it just takes a while to get a version of V8 fully integrated and operating correctly on all platforms -- and I think it would be valuable for the core team to blog…

The io.js team is working alongside the V8 team to make sure that the upgrades are as easy as possible.

Rod Vagg has a project called NAN[0] to try and allow node modules to compile across node versions.

[0] https://github.com/rvagg/nan

Re: Node v0.12.0 (Stable)

#44

Post by 0xFFC »

Touche wrote: post #10
prottmann wrote: post #9

Earlier quoted context omitted.

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.

I am neither side of this fight , Can you explain what is this V8 api story ? seems this is root of all fight in *.js community

Re: Node v0.12.0 (Stable)

#45

Post by dikaiosune »

bshimmin wrote: post #19
antouank wrote: post #8

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

Not sure if this is a joke, but assuming it's not - it's the standard now, and it's been out for... 2 whole months?!

For us JS bystanders who get whiplash from release announcements, I think it's pretty hilarious. I definitely read it as a joke.

Re: Node v0.12.0 (Stable)

#46

Post by oso2k »

bcantrill wrote: post #28
nailer wrote: post #26

Earlier quoted context omitted.

How does the stability concern gel with a unmaintained v8?

The idea of a "maintained" V8 is a bit of a myth -- there really isn't such a thing. Mostly, when V8 breaks node.js (e.g., by changing/eliminating a C++ API or by implicitly or explicitly breaking debugging support), node.js has to change. In that regard, it just takes a while to get a version of V8 fully integrated and operating correctly on all platforms -- and I think it would be valuable for the core team to blog…

That's not true and the v8 team's stance is pretty clear. The master branch is the only "fully supported" code base, currently at 4.2.56 [0]. Most other tagged versions going back a year or two receive best effort support. Usually, that means Ben Noordhuis, but often Andreas, Yang, Vyacheslav, and others on the v8-users and & v8-dev lists. Good responses all around in general. And the list of responsive people continues to grow.

[0] https://github.com/v8/v8-git-mirror/tree/4.2.56

Post reply on HN