3 ms·
TypeScript: Every minor version has breaking changes and the next version after `n.9` is `(n+1).0`
by jp3141 6y ago
TypeScript: Every minor version has breaking changes and the next version after `n.9` is `(n+1).0`
- ZephyrBlu 6y agoThey never go higher than .9? Why?!
- jp3141 6y agoApparently for markting reasons. https://github.com/Microsoft/TypeScript/issues/14116#issuecomment-280592571 https://github.com/Microsoft/TypeScript/issues/14116#issueco...
- ZephyrBlu 6y agoWow. Also pretty funny that he says "if we followed semver rules exactly, literally every single release would be a major version bump". Seems like quite a blase approach to the development of such a large project.
- leetrout 6y agoI always ask teams that say that: "OK, so every release will be major, what's the problem?" I don't think anyone is losing sleep that we're on Chrome 86.0.4240.75 and that communicates exactly the amount of information I need to know if that's older or newer than another version. I agree it's not semantic versioning, per se, and maybe not nice to developers but it's at least communicating clearly IMO.
- rabidrat 6y agoI'm on version 83.0.4103.116 which is 3 major versions behind. I am averse to upgrading because it's working for me and I'm concerned about 3 rounds of incompatible/breaking changes. I have no idea about the relative maturity of the two versions, how big the breaking changes are or if they're likely to affect me, or how much time has transpired between the two versions. With every "major release" of Chromium my wariness increases, until the only way you'll get me to upgrade is when I'm forced to upgrade my system. How is this communicating clearly or being helpful to me? Does anyone know offhand what major version of Chromium/Firefox they're using? If it's just an incremental counter, then why do we need .0.4103.116?
- Raphael 6y ago4240 - 4103 = 137 days between versions.