Today we're thrilled to announce our effort to port the TypeScript compiler and language service to native code, gaining a 10x speed boost in build times and editor responsiveness!
https://devblogs.microsoft.com/typescript/typescript-native-port/
https://devblogs.microsoft.com/typescript/typescript-native-port/
Comments
Bad phrasing on my part. There's no sense waiting. I do wish an actually modular component-model was production ready & widely used, such that a more polyglot & modular future could be taking root here. But, again, no sense waiting for that.
but you're not going to ship or deploy unminified code
the TS compiler was never enough to build most projects - you likely need loaders for CSS, SVG, etc.
most of the community uses the TS compiler only for IDE support (if they want that to change, we need official extension APIs)
https://github.com/microsoft/typescript-go/discussions/458
what happens to the considerable ecosystem of compiler extensions that rely on the unofficial APIs? will Node bindings to the Go version provide the same extension points?
https://bsky.app/profile/filippo.abyssdomain.expert/post/3lk7uzzezvk2d
And if you were wondering, just like I immediately did, why they chose Go and not Rust, the answer is in the video at 2'38.
1. why the educated decision to use go? I thought we collectively decided to rewrite the web in Rust
2. will Doom run and how is the framerate
I am team 2, because let’s be honest we are not all reading the typescript checker code at all
Congrats to the team! This is huge