Hacker News Reader

Yes, but it breaks some cases. I'd recommend to wait 5.7.1 (https://github.com/nodejs/node/issues/5400)

Probably an ignorant question but this makes me wonder: how can they release when their tests don't pass?

Break early, break often :-).

Maybe psychology...

People won't use x.y.0 so they build in a bug to push to x.y.1 afterwards

I haven't been following, but it looks like the tests were passing and they just didn't have tests to prevent these issues that came up.

This is exactly why I've stayed away from this stack wherever possible!

I hope you stay away from GCC as well, which for example broke C++ in 4.7.0 and fixed it in 4.7.2.

Any new major release is bound to break something for someone. Prudence suggests adopting a major release only after a few months. This applies to all platforms.

This is not true. Some platforms, such as Clojure, are usually very stable once released, and there is rarely the need for point releases, as the code was stabilized during the alpha/rc periods.

You're right; I was a bit harsh. I'm just really conservative platform-wise - Node is just starting to get there.

The Node/npm ecosystem does still feel a bit wobbly as an application platform, though, kind of like Ruby was five years ago...

Reply on news.ycombinator.com