v0.10 comes after v0.8(0)? That's like launching Chrome v3 after Chrome v25.
What’s new in Node v0.10?
11–20 of 52 posts
Thus why versions should be stored as strings or several integers, not floats.
Re: What’s new in Node v0.10?
#12v0.10 comes after v0.8(0)? That's like launching Chrome v3 after Chrome v25.
Not sure if trolling…
Re: What’s new in Node v0.10?
#13huh so these strongloop guys are the new node maintainers?
Re: What’s new in Node v0.10?
#14v0.10 comes after v0.8(0)? That's like launching Chrome v3 after Chrome v25.
Re: What’s new in Node v0.10?
#15So 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?
Re: What’s new in Node v0.10?
#16Re: What’s new in Node v0.10?
#17Re: What’s new in Node v0.10?
#18Re: What’s new in Node v0.10?
#19Re: What’s new in Node v0.10?
#20Earlier quoted context omitted.
I agree, if they're doing that, then v0.8 should actually have been v0.08
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?
Actually, I prefer the YY.MM format of versioning (like Ubuntu .)