3 ms·
I believe you are using the wrong metric to measure software maturity.
by jared314 13y ago
I believe you are using the wrong metric to measure software maturity.
- JDDunn9 13y agoWhat's the right metric? Pre 1.0 typically means the software is still in beta. I realize node.js is used by many sites and large sites, but if it is stable/reliable the versioning should reflect that.
- kintamanimatt 13y agoAs with people, pay attention to what it does rather than what it says. The right metric is action, not words or labels!
- samspot 13y agoThere is an annoying trend in software where the devs want 1.0.0 to be the final version. Look at c3p0.
- angersock 13y agohttp://semver.org/ http://semver.org/
- jared314 13y agoCan you expand on that any further? I can't tell what you are trying to say, because my comment was made in awareness of Semantic Versioning. While I support a de facto standard around the meaning of version numbers, you must judge a project's version number by the versioning rules the development team communicates. By the Semantic Versioning Specification's own guidelines, Node.js should be at least at v1.0.0, but the developers have decided against it. Therefore, when judging the stability and maturity of Node.js by the version number alone, you can only compare it to previous releases of Node.js.
- elwell 13y agoIn the "Semantic Versioning Specification", it's seems inconsistent when you look at #4 and #5 and compare it to rule #1 at the top. Changes in x (x.y.z) should be reserved for "when you make incompatible API changes", but the #5 in the spec forces you to change x (to 1) even in some situations where there may not be "incompatible API changes".