News for hackers. Stuff that matters.

A comment on /story/47408727. Parent comment

Re: by matt_kantor on Tuesday March 17, 2026 @08:07PM (#47420089)
How is it used in the wild, in your experience? Have you observed projects following some alternate set of rules?

I thought projects that stay on 0.x.y forever mostly do it because it means they're allowed to break things. Also, since 0.x.y means "anything goes", projects can introduce their own conventions within that range without violating the spec.

I know that some package managers (including Cargo and npm) confusingly treat 0.1.0 → 0.1.1 like a "minor" update, despite the spec. Is this what you're referring to?

[ Parent | on HN ]
Re: by olivia-banks on Friday March 20, 2026 @11:30AM (#47456019)
Yes, that was what I was referring to, although I thought the reason of staying at 0.y.z was more of a cultural one. v0, at least to me, implies that the API may change arbitrarily and quickly, but makes no assertions about the actual versioning scheme itself.

There's a website making fun of it: https://0ver.org/

[ Parent | on HN ]