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

71–80 of 81 posts

Re: Node v0.12.0 (Stable)

#71

Post by wereHamster »

Kiro wrote: post #62
wereHamster wrote: post #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.

> I'm sharing part of my code between server and client How? And why is it a problem with node but not iojss?

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.

Re: Node v0.12.0 (Stable)

#72

Post by wereHamster »

z3t4 wrote: post #70
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…

Most people will appreciate stability more then language features. I'm a bit surprised about some of the comments here.

How do you know? Was there a poll recently about who prefers stability over progress?

Re: Node v0.12.0 (Stable)

#73

Post by LukeB_UK »

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 read HN, I had no idea who he was. I'm not ignorant, I just don't care much about 'celebrities'.

Re: Node v0.12.0 (Stable)

#74

Post by kolev »

inglor wrote: post #63
kolev wrote: post #47

Competition at its best! Days after io.js gets released, node.js outs a major release.

With a year and a half old engine, worse performance and none of the new language features like generators :D

It's true, but they are mobilizing, which is good.

Re: Node v0.12.0 (Stable)

#75

Post by [deleted] »

maratd wrote: post #66
Kiro wrote: post #62

Earlier quoted context omitted.

> I'm sharing part of my code between server and client How? And why is it a problem with node but not iojss?

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.

[deleted]

Re: Node v0.12.0 (Stable)

#76

Post by z3t4 »

wereHamster wrote: post #72
z3t4 wrote: post #70

Earlier quoted context omitted.

Most people will appreciate stability more then language features. I'm a bit surprised about some of the comments here.

How do you know? Was there a poll recently about who prefers stability over progress?

I think mostly about the end users, those who depend on the software.

The last thing you want is to get some weird errors because of a bug in the latest V8 engine. Those bugs tend to never show in development, and is not found in unit testing. But will show up in production when you have thousands of people using it. And there's often nothing you can do about them, then maybe downgrading, or wait for the next Node.JS version.

Re: Node v0.12.0 (Stable)

#78

Post by IsaacSchlueter »

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?

Sure, but no worse (or even all that different) from any other Node release. The community will gradually upgrade, and it'll be fine.

You don't see many people using `node.http.cat()` any more, for example. And yet the community survived ;)

Re: Node v0.12.0 (Stable)

#79

Post by IsaacSchlueter »

ZoneGhost wrote: post #25
antouank wrote: post #8

Meh, 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.

Modules are quickly switching to using nan, which is required anyway for working with both 0.10 and 0.12, so io.js merely accelerated the incentive to use it.

As far as "big sites", several are starting to roll out io.js deployments. Most places don't blog about every upgrade to every internal piece of infrastructure. If you're doing the SOA thing properly, you can start rolling out io.js for new services without removing the versions of node used for other stuff.

At npm, we have some io.js, lots of node 0.10, erlang, java, spidermonkey, python, redis, postgres, etc. It's pretty common to use different stuff side by side in little servers that talk to one another. Less dramatic to talk about than pretending your'e gonna make some big switch-over though.

Re: Node v0.12.0 (Stable)

#80

Post by [deleted] »

dap wrote: post #24

I'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. [0] https://www.joyent.com/developers/node/debug/mdb [1] https://github.com/joyent/node/issues/8718

[deleted]
Post reply on HN