Heads up, TS neither uses semantic versioning (all versions have breaking changes) nor "landmark" versioning - where a major version bump represents some big new feature. 4.0 is just the version that comes after 3.9 in their numbering scheme. (Just like 3.0 came after 2.9, and 5.0 will come after 4.9)
So other than the nice little retrospective at the top of the post, there isn't really any special significance to 4.0.
Still a nice set of changes; the editor improvements are especially welcome.
The trade-off for getting millions of dollars of engineering investment in the TypeScript project is that marketing gets to control version numbers to a certain extent.
It's not really an unalloyed good anyway. If we followed semver rules exactly, literally every single release would be a major version bump. Any time we produced the wrong type or emitted the wrong code or failed to issue a correct error, that's a breaking change, and we fix dozens of bugs like that in every release. The middle digit just isn't useful for TypeScript in a strict semver interpretation.
Certainly annoying, but no one would pay as much attention to TS releases if we were at v40 already. Given that TypeScript is a pretty central part of the ecosystem it's acceptable pain imo, but I really hope that no other, smaller package authors see that and decide to ignore semver because TS does.
I wouldn’t say that fixing a bug should require a major version bump.
I don’t remember where but Rust has a document that outlines the kinds of changes that are considered breaking. It explicitly states that fixing soundness bugs isn’t considered a breaking change even though it might require users to change their code.
Microsoft has a weird history with version numbers... Windows 9 would have broken a LOT of backward compatibility because people did version[0] == '9' to check if you were running Windows 95/98... So they skipped it for Windows 10.
Here's some code from the Jenkins CI project (one of their official plugins, to be precise) that would have thrown an assertion for "windows 9" (which wouldn't have had a version starting with "4.1"), and when assertions were disabled would have identified it as windows 98.
if (name.startsWith("windows")) {
name = "windows";
if (name.startsWith("windows 9")) {
if (version.startsWith("4.0")) {
version = "95";
} else if (version.startsWith("4.9")) {
version = "me";
} else {
assert version.startsWith("4.1");
version = "98";
}
891
u/Retsam19 Aug 20 '20
Heads up, TS neither uses semantic versioning (all versions have breaking changes) nor "landmark" versioning - where a major version bump represents some big new feature. 4.0 is just the version that comes after 3.9 in their numbering scheme. (Just like 3.0 came after 2.9, and 5.0 will come after 4.9)
So other than the nice little retrospective at the top of the post, there isn't really any special significance to 4.0.
Still a nice set of changes; the editor improvements are especially welcome.