3 ms·

I'm not sure why you think version number is any indicator of quality. In any case, npm is 1.4.4 on my machine.

by iends 13y ago

akerl_ 13y ago
As per semantic versioning, 0.x.y is for development. That's not to say that code quality will be necessarily lower, but the API and functionality is expected/allowed to fluctuate prior to 1.0.0. For more info on semantic versioning: http://semver.org/spec/v2.0.0.html http://semver.org/spec/v2.0.0.html Your point regarding npm itself being beyond 1.0.0 is fully valid, I just wanted to clarify the reason for certain expectations existing based on version number.
- iends 13y ago
  node does not use semantic versioning.
  - akerl_ 13y ago
    Having looked, I can't find any link citing that one way or the other, but that doesn't change the fact that enough things these days do adhere to semantic versioning that many people expect certain things based on the version number.
    - nilved 13y ago
      node.js decided uses very non-semantic versioning. It's genarally understood that a 0.x release isn't production-ready, but node.js is widely considered production-ready and in fact every even-numbered release below 1.0 is considered stable. That's a pretty arbitrary and nonsensical scheme if you ask me, but you're not. The bottom line is that backwards incompatible changes aren't expected for a 0.x.y release where x is even.
  - 1stop 13y ago
    Then there shouldn't be an expectation that it is "enterprise ready" at all, right? :P
1stop 13y ago
I don't think it's an indicator of quality. But "enterprise readiness" (whatever that means) which is what Rob the random commenter was talking about in his comment, seems silly on a runtime that is below version 1.0 Yes npm is 1.4.4, but node is 0.10.25. So an expectation of ANYTHING being "production ready" on a non-production ready runtime seems fraught. I get that nodejs is high quality and it is run in production all over the place (I myself run it, and even meteor in production applications). But I understand there are risks and it's a fast moving target.

I'm not sure why you think version number is any indicator of quality. In any case, npm is 1.4.4 on my machine.

by iends 13y ago

I'm not sure why you think version number is any indicator of quality. In any case, npm is 1.4.4 on my machine.

As per semantic versioning, 0.x.y is for development. That's not to say that code quality will be necessarily lower, but the API and functionality is expected/allowed to fluctuate prior to 1.0.0. For more info on semantic versioning: http://semver.org/spec/v2.0.0.html http://semver.org/spec/v2.0.0.html Your point regarding npm itself being beyond 1.0.0 is fully valid, I just wanted to clarify the reason for certain expectations existing based on version number.

iends 13y ago
node does not use semantic versioning.
- akerl_ 13y ago
  Having looked, I can't find any link citing that one way or the other, but that doesn't change the fact that enough things these days do adhere to semantic versioning that many people expect certain things based on the version number.
  - nilved 13y ago
    node.js decided uses very non-semantic versioning. It's genarally understood that a 0.x release isn't production-ready, but node.js is widely considered production-ready and in fact every even-numbered release below 1.0 is considered stable. That's a pretty arbitrary and nonsensical scheme if you ask me, but you're not. The bottom line is that backwards incompatible changes aren't expected for a 0.x.y release where x is even.
- 1stop 13y ago
  Then there shouldn't be an expectation that it is "enterprise ready" at all, right? :P

1stop 13y ago

I don't think it's an indicator of quality. But "enterprise readiness" (whatever that means) which is what Rob the random commenter was talking about in his comment, seems silly on a runtime that is below version 1.0 Yes npm is 1.4.4, but node is 0.10.25. So an expectation of ANYTHING being "production ready" on a non-production ready runtime seems fraught. I get that nodejs is high quality and it is run in production all over the place (I myself run it, and even meteor in production applications). But I understand there are risks and it's a fast moving target.