5 ms·
Yes, but it breaks some cases. I'd recommend to wait 5.7.1 (https://github.com/nodejs/node/issues/5400 https://github.com/nodejs/node/issues/5400)
by btd 11y ago
Yes, but it breaks some cases. I'd recommend to wait 5.7.1 (https://github.com/nodejs/node/issues/5400 https://github.com/nodejs/node/issues/5400)
- amelius 11y agoProbably an ignorant question but this makes me wonder: how can they release when their tests don't pass?
- johnchristopher 11y agoBreak early, break often :-).
- k__ 11y agoMaybe psychology... People won't use x.y.0 so they build in a bug to push to x.y.1 afterwards
- mc808 11y agoI 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.
- samcheng 11y agoThis is exactly why I've stayed away from this stack wherever possible!
- jzwinck 11y agoI 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.
- loevborg 11y agoThis 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.
- samcheng 11y agoYou'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...