Watch TypeScript creator Anders Hejlsberg on The Peterman Pod

Following the release of TypeScript 7.0, Hejlsberg joins host Ryan Peterman to discuss the process of porting from JavaScript to Go, the pros and cons of agentic AI for coding, and more. How does a team tackle the port of one of the most.

The TypeScript team worked for more than a year on a native port built in Go that could make the most of modern hardware. The port maintained the structure and logic of the original codebase to keep results consistent and compatible between the two.

What Happened

The key difference: TypeScript 7 brings native code speed, shared memory multithreading, and several new optimizations that typically yield increased speeds of between 8x and 12x on full builds. Next, the team had to decide on a programming language for the port.

• Dive into a detailed conversation that breaks down the news from Build and what it means for the developer ecosystem.

• The leader of the new Microsoft Security FORGE (Frontier Offensive Research & Generative Exploitation) Labs, Kim takes us behind the scenes of codename MDASH and explains why a multi-model agentic approach may be the.

• Now, the team uses AI daily in its work: helping to write tests, move pull requests, and more.

Key Details

After looking at some core assumptions made by the TypeScript codebase—the presence of garbage collection as well as the first-class treatment of functions, for example—Go emerged as the clear winner. While that approach was integral to the port, early testing and community.

• As for working with AI, Hejlsberg called out that LLMs are stochastic—something we should all keep in mind as we determine when and where to deploy these tools.

• That gave them code with no syntax errors, but it didn’t properly compile.

• Once convinced that 10x performance gains were possible, they wrote a tool that syntactically translates TypeScript into Go.

Why It Matters

Early versions of TypeScript 7.0 were also tested internally at scale by Bloomberg, Canva, Notion, Sentry, Slack, and Vanta, with strong results.

• The team wrote its prototypes, including the scanner and parser, manually.

• Interestingly, agentic AI didn’t play much of a role in the port—a fact that Hejlsberg chalks up to timing.

What Reports Say

Coverage of the story so far points to:

• Continued reporting by Microsoft as more details emerge