yeaaaahh, speak to me when you have a RC
Node v0.12.0 (Stable)
21–30 of 81 posts
Re: Node v0.12.0 (Stable)
#22As 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?
io.js is built against a much more current version of V8, which notably has default-on support for a lot of ES6 stuff.
Quite frankly, as a casual node user myself, I'm sticking with node v0.10 for the time being. I want to see how everything shakes out, and my site runs okay for now.
Re: Node v0.12.0 (Stable)
#23Several 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…
Why don't you push nodejs forward and track the latest v8 (or whatever the latest stable chrome is using), and then cut LTS releases at regular intervals, kindof like the kernel or ubuntu?
Also, are these tests public? How many does iojs pass/fail?
Re: Node v0.12.0 (Stable)
#24I'm really excited that this version of Node includes updates I made for the debugger module[0], including the ability to show you the closures in your program[1]. (This has already helped nail some memory issues in Node itself.) I hope to blog about it in more detail next week.
Re: Node v0.12.0 (Stable)
#25Meh, too late. io.js is the standard now.
iojs is definitely not the "standard" by any means... It's accelerating at a quick pace, but I haven't heard of any major sites making the switch yet. Many native modules (node-gyp compiled) aren't functioning yet, and the streams module was a bit finicky as of a couple weeks back. I'm looking forward to the market competition actually. Can't go wrong with having two standards battle to be the best.
Re: Node v0.12.0 (Stable)
#26Several 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…
How does the stability concern gel with a unmaintained v8?
Re: Node v0.12.0 (Stable)
#27Several 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…
Why don't you push nodejs forward and track the latest v8 (or whatever the latest stable chrome is using), and then cut LTS releases at regular intervals, kindof like the kernel or ubuntu? Also, are these tests public? How many does iojs pass/fail?
That is the plan for io.js. Doing releases often and LTS at some interval.
Re: Node v0.12.0 (Stable)
#28Several 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…
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 some of the history and technical details here...
Re: Node v0.12.0 (Stable)
#29Earlier quoted context omitted.
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.
Example? I'm curious because mostly everything has worked for me. I'm using: io.js v1.1.0 npm v2.4.1 node-gyp v1.0.2
fibers
Re: Node v0.12.0 (Stable)
#30As 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?
io.js is built against a much more current version of V8, which notably has default-on support for a lot of ES6 stuff. Quite frankly, as a casual node user myself, I'm sticking with node v0.10 for the time being. I want to see how everything shakes out, and my site runs okay for now.
I think the next security "situation" in node and/or io will be a key decision point for many of us in similar situations.