Since its launch in 2012, TypeScript has become a key player in the JavaScript ecosystem.
Its static typing and tooling have made it a favorite for large-scale applications.
However, its compiler, which runs on Node.js, has some limitations in terms of performance.
That's why Microsoft made a major decision: move the TypeScript compiler to Go. But why Go and not Rust or C++?
Why TypeScript is moving away from JavaScript
Currently, the TypeScript compiler (which you use with the tsc command) is deeply integrated with... TypeScript! This deep integration has led to several limitations:
- A dependency on Node.js: Each execution of the compiler requires a Node.js runtime;
- Performance limitations: Large projects experience longer compilation times;
- A significant memory footprint: The compiler consumes a lot of memory.
Why Go was chosen over Rust or C++
Rust
Too complex for a simple port, more suited for a complete rewrite.
C++
Too low-level (requiring too much effort to manage memory/avoid leaks).
The reasons for choosing Go
Finally, it's Go that was chosen for this port.
With its fast compilation, its memory management, and its simple syntax, Go allows Microsoft to offer a native version of TypeScript as fast as possible! 👀
Ultimately, it's the best choice for a smooth transition!
Impact on the TypeScript ecosystem
Microsoft has planned several steps before the complete rollout:
Mid-2025
Experimental version of the native compiler available.
Testing under real-world conditions on large projects.
End of 2025
Stable version integrated into TypeScript 7.0.
Gradual adoption by Microsoft tools.
Developers will have time to test the Go version during the transition phase.
2026 and beyond
Porting of the Playground and other tools to Go.
Final phase of transition to the native compiler.
Developers will be able to test the Go version during the transition phase.
Conclusion
With TypeScript's move to Go, Microsoft offers a significant performance boost to developers. Compilation times are divided by 10, memory management is improved, and overall performance is greatly enhanced.
What this means for you:
- You save time on each build.
- You can work on more fluid projects without slowdowns.
- You benefit from a smooth transition with TypeScript 6.x compatibility.
TypeScript continues to evolve and this change marks a new era for the language. Stay tuned, and don't hesitate to follow our comprehensive TypeScript training!
FAQ
Can I still use TypeScript 6.x?
Yes! 😗 Microsoft will maintain the JavaScript version for several years!
How can we test the Go version?
An experimental version will be available mid-2025 for the first tests!
Will the TypeScript syntax change?
No, TypeScript remains the same.
How to stay updated on the latest TypeScript news?
By following our comprehensive TypeScript training.
