ZeroVer: 0-Based Versioning
0ver.org
ZeroVer: 0-Based Versioning
1–10 of 91 posts
Re: ZeroVer: 0-Based Versioning
#2I can’t tell if this is serious or satire. There’s no spec.
Re: ZeroVer: 0-Based Versioning
#3I can’t tell if this is serious or satire. There’s no spec.
It's obviously satirical. If so, the author is brilliant. Otherwise, well...
I mean just look at the project show cases. Included are the usual colossal cluster^Wframeworks that power our decaying software infrastructure.
Personally, I don't trust anything that either stays perpetually under v1.0 or exceeds v10-15.
Re: ZeroVer: 0-Based Versioning
#4I can’t tell if this is serious or satire. There’s no spec.
It should be satire, but it is serious. The spec is SemVer, but only versions starting with a zero are allowed. This just shows that SemVer is bullshit.
Re: ZeroVer: 0-Based Versioning
#5Somehow we need a less horrible SemVer or a less horrible social contract around SemVer.
Re: ZeroVer: 0-Based Versioning
#6I can’t tell if this is serious or satire. There’s no spec.
Satire, for sure. Check the about page. That said with the number of projects on this list, it might as well be serious.
Re: ZeroVer: 0-Based Versioning
#7I can’t tell if this is serious or satire. There’s no spec.
It's obviously satirical. If so, the author is brilliant. Otherwise, well... I mean just look at the project show cases. Included are the usual colossal cluster^Wframeworks that power our decaying software infrastructure. Personally, I don't trust anything that either stays perpetually under v1.0 or exceeds v10-15.
There's no point in calling it 1.0 unless you want to break compatibility with 0.x. Sometimes you get the design right on day 1, I guess.
Re: ZeroVer: 0-Based Versioning
#8I noticed this the other day while writing a small server in Python. FastAPI is 0.100, fine. But I was surprised to find:
- Uvicorn is 0.22
- httpx is 0.24
- starlette is 0.28
And so on and on. More generally, the quality of Python's tooling and ecosystem is astonishingly low compared to the investment that every day pours into it.
Re: ZeroVer: 0-Based Versioning
#9Earlier quoted context omitted.
It's obviously satirical. If so, the author is brilliant. Otherwise, well... I mean just look at the project show cases. Included are the usual colossal cluster^Wframeworks that power our decaying software infrastructure. Personally, I don't trust anything that either stays perpetually under v1.0 or exceeds v10-15.
There's no point in calling it 1.0 unless you want to break compatibility with 0.x. Sometimes you get the design right on day 1, I guess.
In SemVer, you can break compatibility with 0.x within 0.x. 1.x is the promise that there won't be any future compatibility breaks within the 1.x series.
Re: ZeroVer: 0-Based Versioning
#10I can’t tell if this is serious or satire. There’s no spec.
It's satire. If you're unsure, have a look at their about page [1]. They are criticising the idea of staying on a 0.x release for years even though your project is long used in production by now.