[cbdfghh]

>It's much more reasonable though: they're committed to using Semver, so even a minor breaking change (like upgrading Typescript) will bump the version number. So they're expecting the version numbers not to matter as much anymore, similar to how you no longer think of the version number of Chrome or Firefox too often.

That's contradictory.

Once you introduce breaking changes, you require people to update, and old code may not work on new systems.

Then you can't just say "Angular" like you can't say "Python" or "C/C++"

[klodolph]

I know what you mean but it's kind of ridiculous to say that "you can't say 'Python'". There's a reason why the project name doesn't change just because you bumped the major version number.

[cbdfghh]

>There's a reason why the project name doesn't change just because you bumped the major version number.

The OP suggested to make an "evergreen" Angular, like an evergreen Chrome. My point is that you can't do that if you introduce breaking changes, because "this will work in C (and just upgrade to a new version if you don't have it)" doesn't work anymore.

Obviously making small breaking changes shouldn't require renaming your language (so PHP4 is still PHP, even though it broke quite a lot of old files relying on register_globals)