TypeScript 5.0
Without Angular, we may very well not have TypeScript today.<p>The top thing listed in this release (TypeScript doesn&#x27;t follow semver, btw) is about Decorators.  I find the whole story about Angular&#x27;s role in TypeScript early days to be very fascinating because I don&#x27;t hear people talk about it anymore (just search &quot;AtScript TypeScript&quot; if you weren&#x27;t around at the time).  It was the Angular team that forced Decorators to be added when it was still stage 0.  In exchange, they forfeited continued work on their would-be competitor to TypeScript.<p>Even without the Decorators thing, Angular was intensely popular and it made a big impact how they went &quot;all in&quot; on TypeScript, pushing a lot of early adoption.  I know lots of people that first started with TypeScript because of work on an Angular project.<p>I think a lot of people don&#x27;t seem to know&#x2F;remember how touch-and-go TypeScript was in the very early days.  There were many large projects that were all-in on FlowType, and others still that were pushing for Elm, etc.  For example, it took quite a while for you to be able to do JSX _at all_.<p>Today, we just have TypeScript.  Well.  I do know one company that uses ReasonML (or isn&#x27;t it called Rescript now?)<p>---<p>Historical stuff aside, I&#x27;m extremely happy we ended up with TypeScript over the others because the team is so incredibly awesome and dedicated.  It&#x27;s rare you see such a large project so well shepherded by such a talented set of individuals.  It speaks volumes that the average tenure on that team is so high.  We&#x27;ve seen some public apologies from the Flow team on this topic so I don&#x27;t feel like I&#x27;m talking behind anyone&#x27;s back if I say they ended up truly not being up to the task of being what TypeScript is today.