Microsoft goes nuclear on TypeScript codebase…

Microsoft is accelerating the TypeScript compiler by rewriting it in Go, aiming to eliminate a core performance bottleneck: TypeScript’s compiler is written in TypeScript, which limits low-level optimization. The practical result is a major speedup—Microsoft reports cutting VS Code TypeScript compile time from 70 seconds to 7 seconds, with similar ~10x improvements across other projects. For developers, that translates into faster feedback loops in large codebases and less editor lag when working with big TypeScript projects.

The change is also framed as a “port,” not a brand-new implementation from scratch. Microsoft plans to convert the existing TypeScript codebase line-by-line into equivalent Go code, preserving the compiler’s behavior and semantics. That means the same kinds of compiler errors and edge-case behavior should remain—just delivered much faster. The rewrite targets the long-term goal of making TypeScript’s tooling more responsive without changing what developers already rely on.

Why Go? The key technical reasons are performance portability and compilation model. Unlike Java or C-style toolchains that typically compile to bytecode running on a virtual machine, Go compiles directly to optimized machine code for different chip architectures. Go also includes automatic memory management via garbage collection, which can reduce the complexity of manual memory handling compared with C++ or Rust. Microsoft’s choice of Go—rather than sticking with an in-house language or jumping onto Rust or Zig—signals a focus on engineering constraints: the compiler needs to run fast across platforms, and the implementation language must support that efficiently.

The timeline matters. The rewrite is not expected to ship immediately because TypeScript is currently at version 5.8, while Microsoft isn’t planning a release until TypeScript 7. Even then, adoption could take months or longer as the ecosystem transitions.

For developers, the immediate takeaway is that TypeScript performance issues tied to compiler speed should improve substantially, especially in editors like VS Code and in large repositories. The longer-term takeaway is that Microsoft is willing to break with language loyalty—using a language associated with Google rather than a Microsoft-first option—to fix a foundational tooling problem. When the new compiler lands, the same TypeScript experience should feel dramatically snappier, with faster builds and fewer productivity hits from slow typechecking.