Node v0.12.0 (Stable) • Hacker News Board

Re: Node v0.12.0 (Stable)

#51

Post by dmpk2k » Sat, Feb 07, 2015, 1:51 AM UTC

LukeB_UK wrote: post #42

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.

He probably should, but then, almost everybody using both node and HN knows who he is.

Re: Node v0.12.0 (Stable)

#52

Post by shadowmint » Sat, Feb 07, 2015, 2:48 AM UTC

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…

There's certainly something to be said for stability, but node continues to use abandoned versions of the V8 engine, which, increasingly, is going to be a problem.

Software does tend to remain stable if you never make any changes to it, but that's not necessarily the right path.

Oh well, if nothing else, this whole io.js thing has set fire to joyent. It's nice to see something happening at last.

I guess competition is a good thing.

Re: Node v0.12.0 (Stable)

#53

Post by jkrems » Sat, Feb 07, 2015, 2:49 AM UTC

btbuildem wrote: post #49

I would just like to point out people are running production stuff on v0.x of something..

Yes, but what's your point? That version numbers aren't the best indicator for production readiness?

Re: Node v0.12.0 (Stable)

#54

Post by xtrumanx » Sat, Feb 07, 2015, 3:04 AM UTC

dmpk2k wrote: post #51

LukeB_UK wrote: post #42

Earlier quoted context omitted.

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.

He probably should, but then, almost everybody using both node and HN knows who he is.

I don't know why you assume that. Who is he anyways and why do you expect HN+node folks to know who he is?

Re: Node v0.12.0 (Stable)

#55

Post by mattkrea » Sat, Feb 07, 2015, 3:09 AM UTC

jekrb wrote: post #18

Touche wrote: post #10

Earlier 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

Ursa

Re: Node v0.12.0 (Stable)

#56

Post by dmpk2k » Sat, Feb 07, 2015, 3:27 AM UTC

xtrumanx wrote: post #54

dmpk2k wrote: post #51

Earlier quoted context omitted.

He probably should, but then, almost everybody using both node and HN knows who he is.

I don't know why you assume that. Who is he anyways and why do you expect HN+node folks to know who he is?

Amongst other things, Bryan Cantrill is the CTO of Joyent, one of the authors of DTrace, and comments here regularly. If you use node (or DTrace, or ZFS) and read HN, he's pretty hard to miss.

Re: Node v0.12.0 (Stable)

#57

Post by shna » Sat, Feb 07, 2015, 4:21 AM UTC

It's been 5 years since node.js is around? is node.js development slow or the version numbers (scheme) is progressing slow. It sounds like there is at least a decade for ver 1.0. Probably 1.0 does not mean anything. In my mind version 1.0 is the when the product is complete.

Re: Node v0.12.0 (Stable)

#58

Post by skeeterbug » Sat, Feb 07, 2015, 4:38 AM UTC

antouank wrote: post #8

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

I am just curious, what happens when people start writing ES6 io.js modules and posting them to NPM? Won't it be an issue for older versions of node? Is NPM going to start fragmenting because of this?

Re: Node v0.12.0 (Stable)

#59

Post by untog » Sat, Feb 07, 2015, 4:40 AM UTC

dmpk2k wrote: post #56

xtrumanx wrote: post #54

Earlier quoted context omitted.

I don't know why you assume that. Who is he anyways and why do you expect HN+node folks to know who he is?

Amongst other things, Bryan Cantrill is the CTO of Joyent, one of the authors of DTrace, and comments here regularly. If you use node (or DTrace, or ZFS) and read HN, he's pretty hard to miss.

I use Node and Hacker News every day. I have no idea who he is. I'm not some rube, I just don't pay much attention to personalities in tech like that.

Re: Node v0.12.0 (Stable)

#60

Post by olalonde » Sat, Feb 07, 2015, 4:52 AM UTC

skeeterbug wrote: post #58

antouank wrote: post #8

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

I am just curious, what happens when people start writing ES6 io.js modules and posting them to NPM? Won't it be an issue for older versions of node? Is NPM going to start fragmenting because of this?

The npm registry is already used for a bunch of stuff that it wasn't really intended for (e.g. front-end UI components, coffeescript, etc.). One solution for projects that need older versions of node would be to transpile es6 dependencies using https://github.com/esnext/es6-module-transpiler for example.