I don’t think, it’s as conscious of a decision. Projects above a certain level of complexity will just never realistically reach the criteria one might associate with a 1.0 (stable API, no known bugs, largely feature-complete). And then especially non-commercial projects just don’t have an incentive to arbitrarily proclaim that they fulfill these criteria…
https://0ver.org/zerover_0_based_versioning.html
I’ve noticed this and seeing it all laid out is hilarious. (So, so many JS frameworks omg)
Is this basically so they can forever say: “Well don’t expect it to be feature complete, it’s not even 1.0 yet!” ??
I don’t think, it’s as conscious of a decision. Projects above a certain level of complexity will just never realistically reach the criteria one might associate with a 1.0 (stable API, no known bugs, largely feature-complete). And then especially non-commercial projects just don’t have an incentive to arbitrarily proclaim that they fulfill these criteria…
I’m afraid most, if not all, of the projects listed use pride versioning, also.
This is hilarious