A 10x faster TypeScript

Microsoft Developer2 HN recommenders · 2025–2025
608K views · talk · dated · Uploaded 2025-03-11

Anders Hejlsberg introduces the native port of the TypeScript compiler, written in Go, which promises roughly 10x faster tooling. He demos compiling VS Code and explains where the speedup comes from.

Commenters cite it as the authoritative source for why the port is faster and why Go was chosen.

Watch on YouTube

5 comments from Hacker News

@dcre2025 · in “A 10x Faster TypeScript”

In the embedded video they show some of the code side by side and it is just a ton of if statements. [VIDEO]

@dataviz10002025 · in “A 10x Faster TypeScript”

Not sure if it does but the video linked in the post might answer your question? I think he is compiling vscode which includes Monaco editor which is where they are getting 10x faster stat. (I might be wrong here.) [0] [0] [VIDEO]

@odyssey72025 · in “A 10x Faster TypeScript”

The key: > immutable data structures --> "we are fully concurrent, because these are what I often call embarrassingly parallelizable problems" The relationship of their performance gains to functional programming ideas is explained beginning at 8:14 [VIDEO]

RecommendsView on HN
@kristianp2025 · in “Show HN: I rewrote my Mac Electron app in Rust”

Here's the FAQs, where they explain the decision to go with Go and not, say, rust. [LINK] Hejlsberg also says in this video, about 3.3x performance is from going native and the other 2-3x is by using multithreading. [VIDEO]

@yomismoaqui2025 · in “Show HN: Doom port to pure Go – Gore”

After hearing the explanation about why he picked Go for the Typescript compiler I can only be more of a fan of Anders Hejlsber. He said that Go was chosen due to its suitability for the workload, offering low-level control, optimized native code, automatic memory management, and concurrency. And this coming from the same guy that created C#, Typescript, Delphi & Turbo Pascal shows how a real engineer takes a decision of this magnitude. Is Go the best decision for every SW project? No, but in this case the arguments (and the tests they did during their evaluation) check out. And no, picking F# simply because you love the language is not a mature decision. You can check his arguments here: [VIDEO]

RecommendsView on HN