What’s new in Node v0.10?

http://blog.strongloop.com/whats-new-in-node-v0-10/

by sickeythecat • 13 years ago

47 49 13 years ago

blog.strongloop.com

greyelmy• 13 years ago

W00t!

foodog12• 13 years ago

After 9 months all we get is a new streams interface?

dmpk2k• 13 years ago

Given how all manner of languages, libraries and frameworks tend to massively sprawl over time, keeping the growth of core components down is a good idea.

dmethvin• 13 years ago

First, it's a very nice new streams interface. Second, the core functionality can't change that much at this point if people want their old code to work. Read the discussion of streams2 and see how much thought went into avoiding breakage. http://blog.nodejs.org/2012/12/20/streams2/

mtgx• 13 years ago

v0.10 comes after v0.8(0)? That's like launching Chrome v3 after Chrome v25.

untog2• 13 years ago

0.10 != 0.1, in the same way that 0.8 != 0.80

taytus2• 13 years ago

Could you explain that?, because if you're right I been wrong my whole life.

1SaltwaterC5• 13 years ago

v0.8 < v0.10 < ... < v0.80. God damn math.

homeomorphic6• 13 years ago

It's not meant to be a decimal number. A version number is a sequence of natural numbers ordered lexicographically.

neave• 13 years ago

It's major.minor.revision, not decimal.

asafh• 13 years ago

The version is not a decimal but a dot delimited list of integers. Which gives you 10 > 8.

aviraldg2• 13 years ago

I agree, if they're doing that, then v0.8 should actually have been v0.08

epidemian• 13 years ago

What if they happen to reach 100 on the minor version, should they've named it "1.008" just in case? And if it reaches 1000?

aneth4• 13 years ago

Thus why versions should be stored as strings or several integers, not floats.

masklinn3• 13 years ago

Then again, it's not like you can store 0.1.3 as a float.

On the other hand, some version numbers can be stored as floats (kind-of, to a point): Knuth's software is versioned using approximations of irrational numbers, the more digits the later the version. TeX's current version is 3.1415926 and METAFONT's is 2.718281. Both can be stored as floats, although the respective and eventual π and e can't be.

rydgel• 13 years ago

Not sure if trolling…

1SaltwaterC5• 13 years ago

By reading some of the gems around here, apparently not. Example:

> A version number is a sequence of natural numbers ordered lexicographically.

I need a new rage face for expressing this.

cristiantincu2• 13 years ago

http://semver.org/

homeomorphic6• 13 years ago

Version 0.8 isn't version 0.80. A version number is a sequence of natural numbers, ordered lexicographically and written with periods separating elements. The version (x1, x2, ...) compares to the version (y1, y2, ...) as follows: If x1 =/= y1, then whichever of x1 and y1 is bigger decides which version is the highest. Otherwise, recurse and compare the versions (x2, x3, ...) and (y2, y3, ...).

You can think of a decimal number in the same way (well, leaving out some minor technicalities with numbers requiring infinite expansions here), but you then have to allow only numbers between 0 and 9 (inclusive) in your sequence. Let's leave out positive numbers (because otherwise we'd have to grow sequences in both directions from the decimal point, which is an annoying technicality). Then 0.12345 is simply the sequence (1, 2, 3, 4, 5), which in version notation is 0.1.2.3.4.5. On the other hand, decimal 0.80 is version 0.8.0, not version 0.80.

Really, all in all, version numbers are just decimal expansions, except that we leave out the equivalence relation that says that, for example, 10x10^1 is the same as 1x10^2. So while 0.8.0 and 0.80.0 are distinct version numbers, they collapse to the same value as real numbers (or you might want to collapse 0.80.0 to 8.0 -- it doesn't matter, that's all a matter of taste).

IsaacSchlueter5• 13 years ago

It's a 3-tuple, not a float.

mmaster52• 13 years ago

huh so these strongloop guys are the new node maintainers?

cristiantincu2• 13 years ago

“For those looking for commercial support, StrongLoop (Ben Noordhuis & Bert Belder's company) has released a distribution containing node v0.10 that they will support on Windows, Mac, Red Hat/Fedora, Debian/Ubuntu and multiple cloud platforms. You can download their Node distribution here.” —http://blog.nodejs.org/2013/03/11/node-v0-10-0-stable/

IsaacSchlueter5• 13 years ago

No.

StrongLoop employs 2 node core committers, Ben Noordhuis and Bert Belder, who are also two of the most active libuv committers. (They have other folks that work there, of course, but those two also work on Node itself quite a lot.)

Joyent still is the custodian and IP owner of the Node.js project. They pay me to work on node, and also provide the project with marketing, legal, hosting, and other resources. Joyent also uses Node extensively in their technology stack, and builds tools to debug their own and their customers' production Node applications.

StrongLoop will be providing support to users of their Node Distro, which bundles v0.10 with a few battle-tested npm modules.

Joyent and StrongLoop are very different companies, and while they're not officially partners, that I'm aware of, they are certainly not competitors in any sense.

mmaster52• 13 years ago

As I read it, Joyent relicenses the IP under MIT, so although they may be the IP "owner" they immediately give anyone a license to do pretty much whatever with the code.

Definitely appreciate that they pay you to work on it. Appreciate that there are new companies in the ecosystem too.

And finally someone who looks like they are going to support Node on Windows and Linux!

mjs2• 13 years ago

So a readable stream is an EventEmitter, but it's not recommended that you actually listen for 'data' events? (Instead you're supposed to call read()?) That seems ... counterintuitive.

Anyone know what you're supposed to do if you have code with multiple listeners for 'data' events?

IsaacSchlueter5• 13 years ago

If you add a listener for 'data', or call stream.resume() then it'll start flowing data as it receives it, just like v0.8 and before. The only caveat is that listening for 'end' will not automatically start the flow of data, so you do sometimes have to either call resume() or add a data listener.

In practice, it's rare that you care about the end of the stream, but not about the data coming through it, except in tests.

tl;dr Your existing programs will almost certainly Just Work.

mjs2• 13 years ago

Thanks. Is there any significant performance difference? (I'm wondering if it makes sense to roll my own "proxy" converting read()s to emit()s.)

awjr• 13 years ago

Look here for a detailed analysis of benchmarks. http://blog.nodejs.org/2013/03/11/node-v0-10-0-stable/

From that post, their focus is on v0.12 and then v1.0. Nice to see we're getting to that stage.

What’s new in Node v0.10?

Related Stories