2 ms·
> ... but going to v4 in one year isn't as unstable as it sounds; it's just following Chrome's example of not caring how big the version number gets, so long as
by xg15 11y ago
>
... but going to v4 in one year isn't as unstable as it sounds; it's just following Chrome's example of not caring how big the version number gets, so long as the semantics make sense.
Except that Chrome is mainly an application for end users and not a library, so the implications of "breaking changes" are a lot less severe anyway.
In the parts where it does provide APIs (e.g. to websites or add-ons), the compatibility policies are a lot stricter than semver would require.