3 ms·
It's not like you can use SemVer on a browser. Too many changes would make it hard to decide whether things are breaking or not. And due to backwards compatibil
by colejohnson66 5y ago
It's not like you can use SemVer on a browser. Too many changes would make it hard to decide whether things are breaking or not. And due to backwards compatibility, it's possible that we'd actually be on 3.100.0 or whatever. It's a lot easier to just bump the major every 6 weeks with releases.
Is it the best idea? Probably not, but it's something simple that works and is consistent.
- Pxtl 5y agoChrome does have an API - Selenium uses it. And selenium's chrome driver has strict rules about which Chrome versions it supports as it is versioned. So actually Chrome's rapid versioning does reflect the pace of changes to their API.
- colejohnson66 5y agoBut is Selenium’s requirements due to breaking changes actually existing? Or just a lack of effort to test multiple versions?
- kimixa 5y agoArguably with SemVer as html 1.0 pages still work with no compatibility issues, it will still be 1.x if that is the gate for "breaking" changes. The other way, if you rely on experimental features, it's likely you'll be breaking something every release, ending up with effectively a different major version every release - which is arguably pretty much what we have now. The issue is that for a sufficiently complex environment, the definition of a "Breaking" api change depends on what you use - it's pretty hard to end up making any changes that don't have some visibility across the API after all, even internal details end up leaking.