Hacker News Reader

There is a long interview with Anders Hejlsberg here https://www.youtube.com/watch?v=cywK3XYYJ2o&pp=ygUbYW5kZXJzI... where he talks about that, in short from what he said 1-2 months ago, I doubt that they will change directions.

View on HN

Given the Typescript compiler rewrites that keep popping up, Next.js has one, this is another one, Angular just announced they are also going with theirs, eventually there will some community pressure on how the team will proceed.

Note there is already a feedback post from them (currently top one), that they will need to react to this.

Do we know why? Is there some hole the official one isn’t filling? Seems like having 10 different compiler implementations would be a portability nightmare. Now I can’t guarantee my typescript is going to run the same on node/angular/whatever

Yes, one hole is no longer being able to just integrate the Typescript compiler into other tools.

The team has posted reaching feature parity with broken workflows past 7.0 release.

https://blog.angular.dev/an-update-on-angulars-typescript-7-...

https://devblogs.microsoft.com/typescript/announcing-typescr...

Reply on news.ycombinator.com