31–40 of 52 posts
v0.10 comes after v0.8(0)? That's like launching Chrome v3 after Chrome v25.
Thus why versions should be stored as strings or several integers, not floats.
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.
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?
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.
Earlier quoted context omitted.
Could you explain that?, because if you're right I been wrong my whole life.
It probably would have been better to say v0.10 != v0.1, since obviously "0.10 != 0.1" is a misleading statement.
huh so these strongloop guys are the new node maintainers?
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.
v0.10 comes after v0.8(0)? That's like launching Chrome v3 after Chrome v25.
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?
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 test…
Earlier quoted context omitted.
Could you explain that?, because if you're right I been wrong my whole life.
Version numbers are not numbers . How would you explain, for example, Chrome's version 24.0.1312.57? Dots separate logical numberings, like version, patch, bugfix, etc. So 3.0 goes after 2.0 And 2.0.2 after 2.0.1. And 1.10 after 1.9 .
Earlier quoted context omitted.
Thus why versions should be stored as strings or several integers, not floats.
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.
Earlier quoted context omitted.
v0.8 < v0.10 < ... < v0.80. God damn math.
It's not meant to be a decimal number. A version number is a sequence of natural numbers ordered lexicographically.