3 ms·
The thing is, if you're writing software with a lot of breaking changes, SemVer doesn't make much sense, because you'll just quickly get to major version number
by einpoklum 4y ago
The thing is, if you're writing software with a lot of breaking changes, SemVer doesn't make much sense, because you'll just quickly get to major version numbers in the hundreds.
- fourthark 4y agoEspecially when the API surface area is as gigantic as graphviz's. Still, it's great to see new maintainers with bold ideas.
- dragonwriter 4y ago> The thing is, if you're writing software with a lot of breaking changes, SemVer doesn't make much sense, because you'll just quickly get to major version numbers in the hundreds “The version number conveys whether there is a breaking change” seems more important than “the version number remains small”, so while the second half may be true, I don’t see how that supports the first half at all.
- einpoklum 4y agoThe problem isn't that it's small, the problem is that if few changes are breaking, then you have "version 5" which is significantly different than "version 4". Is version 465 very different from version 464 though?
- justsomehnguy 4y ago/me points at Firefox
- ivanche 4y agoA bit unfair, no? Firefox switched to the "new major version every 6 weeks (or so)" only because Google did that first with Chrome, and people started thinking "Chrome is so much better because it's in version 17 and Firefox is version 3".
- justsomehnguy 4y ago> Is version 465 very different from version 464 though?
- ivanche 4y agoAs soon as: a) you precisely define "very different" AND b) versions 464 and 465 of Firefox and Chrome are available, we can continue discussing :)