TypeScript is being rewritten in Go, promising up to 10x faster type-checking and compilation. This article covers what the rewrite means for developers, the performance gains measured so far, and how the transition will work.
Anıl Soylu
The TypeScript world is buzzing! In a move that's got developers everywhere reaching for their coffee (or maybe something stronger), the TypeScript team has announced a complete rewrite of the compiler in Go. Yes, you read that right. Go!
The promise? A staggering 10x to 15x speed improvement in type-checking and compilation. If that doesn't make your ears perk up, I don't know what will.
Why This Matters (A Lot) For years, the cry for better performance has echoed through the TypeScript community. We've all felt the pain of slow IDE feedback, sluggish builds, and CI pipelines grinding to a halt. Several attempts have been made to resolve these issues, but the TypeScript team seems to have nailed it.
This isn't just a minor tweak; it's a fundamental shift that will impact virtually every aspect of the TypeScript development experience:
Blazing-Fast IDEs: Imagine your IDE responding instantly to your every keystroke. Hovers, errors, and auto-completion will become lightning-fast, making coding a joy (yes, a joy!). This applies not only to VSCode, but any editor leveraging the TypeScript language server.
Compiler on Steroids: The tsc compiler, the backbone of TypeScript, is about to get a serious speed injection. Faster local type-checking and builds will translate to more productive development cycles.
CI/CD Nirvana: We all know that type-checking has been the bottleneck in many CI pipelines, even with the advent of super-fast transpilers like esbuild and swc. This rewrite promises to alleviate that pain, making your builds faster and your deployments smoother.
Why Go? (And Not Rust?) The choice of Go might raise a few eyebrows. Why not Rust, the darling of the performance-obsessed? According to the TypeScript team, Go's structural similarity to the existing JavaScript implementation was a key factor. The team will need to work on the current Javascript implementation while developing the new Go version. This means that contributors familiar with the current codebase will be able to transition more easily and contribute to both codebases simultaneously. Here's a comparison shared by Anders Hejlsberg:
When Can We Expect This Magic? The official word is that the Go rewrite is slated for TypeScript 7.0. Given TypeScript's release cadence, that puts it roughly 33 months away. However, and this is my speculation, I suspect we might see a beta version much sooner, perhaps around November 2025. Keep an eye on the typescript-go repo (this is a placeholder since the article doesn't include a link).
What About New Features? Don't worry, the TypeScript team isn't putting the JavaScript version on hold. New features will continue to be added to the existing codebase while the Go rewrite is underway. It's like having your cake and eating it too!
The Bottom Line This TypeScript rewrite is a bold move that promises to deliver a significant boost to developer productivity. While the timeline remains uncertain, the potential benefits are undeniable. Get ready for a faster, smoother, and more enjoyable TypeScript experience!