Re:Show HN: Test your JavaScript modules simultaneously in 3...
by Nadya on Wednesday April 20, 2016 @07:36PM
(#11538540)
>Are all these 32 actually backwards-incompatible?
Node uses semantic versioning [0] and the current release is 5.10.z
The breaking changes can be found here [1] By searching for `SEMVER-MAJOR`. Some seem rather unavoidable for progress (updating dependencies...) and some are for things that have been deprecated. I'm not an expert but it looks like there are several security related changes as well?
In my eyes a backwards incompatible change that breaks a feature that has been deprecated for years or is insecure is a change worth making. Stability is bad if it means remaining insecure.
Node uses semantic versioning [0] and the current release is 5.10.z
The breaking changes can be found here [1] By searching for `SEMVER-MAJOR`. Some seem rather unavoidable for progress (updating dependencies...) and some are for things that have been deprecated. I'm not an expert but it looks like there are several security related changes as well?
In my eyes a backwards incompatible change that breaks a feature that has been deprecated for years or is insecure is a change worth making. Stability is bad if it means remaining insecure.
[0] http://semver.org/
[1] https://github.com/nodejs/node/blob/v5.10.1/CHANGELOG.md