2 HN users recommended this talk2 months2025score 2
Years with an HN recommendation, 2007–2026
Commenters cite it as the authoritative source for why the port is faster and why Go was chosen.
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.
“The relationship of their performance gains to functional programming ideas is explained beginning at 8:14” (HN, 2025)
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 [this video]
Explains performance gains via immutable data and parallelizable problems from 8:14.
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: [this video]
Hejlsberg's reasoning for choosing Go for the TypeScript compiler.
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] [this video]
Demo compiling VS Code explains where the 10x figure comes from.
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. [this video]
Hejlsberg breaks down speedup: native code versus multithreading.
Video list and Hacker News comment labels from HackerTube (prompted by @karpathy), released under ODC-By 1.0, built on the open-index/hacker-news archive. Hacker News data is provided by Y Combinator; comments remain the work of their authors. Video titles, channel names and thumbnails belong to their creators and are shown via YouTube. HackerTube Watch is an unofficial edition. Data export of 2026-10-31.
Plays via YouTube's privacy-enhanced embed
5 Hacker News comments
From the HN archive; up to 20 kept per video, favoring different commenters. Recommendations first.
Read more
Citations, criticism and jokes