Can 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

Can 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.