r/programming • • Aug 20 '20

Announcing TypeScript 4.0

https://devblogs.microsoft.com/typescript/announcing-typescript-4-0/
1.3k Upvotes

236 comments sorted by

View all comments

Show parent comments

1

u/nibord Aug 21 '20

This is incredibly naive. Not everything is a breaking change, there needs to be a way to put out a minor release that only patches a bug that was in the last release. If you as a consumer have to treat every release as a breaking change, you’re less likely to stay up to date and therefore are more likely to remain on a buggy release.

Semantic versioning gives us a common language to express whether a release break something. If all releases are actually breaking, then they can all be “major”. But if you come across a bug that is not a breaking change, you have no way to signal that it’s a main or change and should be picked up right away. It defeats the usefulness of version numbering. It doesn’t exist to promote the next version. Chrome does that to make Microsoft look bad. Other browser followed their numbering system to make it at least seem like they were caught up. But nobody who consumes a browser is concerned with breaking changes—backward compatibility is almost guaranteed with browsers. It’s not like that with languages or libraries.

3

u/StillNoNumb Aug 21 '20

I think everyone here in this comment section understands and agrees with that. But you need to see that no one cares about updates from v37 to v38 - I can guarantee this thread wouldn't be here at 1.3k upvotes if it said "Announcing TypeScript 40". And more than that, no one would care to update. That's bad for both TypeScript as a language and everyone using it.

So really, what we have here is a trade-off - semver gives us the opportunity that we only need to care about one single version format. TS doing their own thing means that we really end up having two version formats, which I would say is still acceptable. However, as soon as smaller packages decide they can do the same, we end up having thousands.

In the end, the reason TS can get away with this is because they're probably the one most central package on NPM. This means that they can afford to market their versioning, but it also means that they need to market their versioning - because new versions of TS usually contain very important changes.

1

u/Multipoptart Aug 26 '20

Not everything is a breaking change

Every release of TypeScript has a change wherein some code that compiled on the previous version no longer compiles on the new version. That's how compilers work.

0

u/nibord Aug 26 '20

That’s not how compilers work.