A 10x faster TypeScript
Microsoft Developer2 HN recommenders · recommended in 2 months, 2025–2025
talk · intermediate · 2025–2025 on HN
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.
Up next
13 mo on HNRich Harris - Rethinking reactivity
You Gotta Love Frontend
15 HN recommender · 2019–2026
12 mo on HNLexical Scanning in Go - Rob Pike
GoogleFOSSSydney
13 HN recommender · 2012–2025
12 mo on HNWilliam Byrd on "The Most Beautiful Program Ever Written" [PWL NYC]
PapersWeLove
11 HN recommender · 2017–2026
10 mo on HNCppCon 2016: Jason Turner “Rich Code for Tiny Computers: A Simple Commodore 64 Game in C++17”
CppCon
13 HN recommender · 2016–2024
8 mo on HNClasp: Common Lisp using LLVM and C++ for Molecular Metaprogramming
Google TechTalks
8 HN recommender · 2015–2024
7 mo on HNCompiling C to printable x86, to make an executable research paper
suckerpinch
8 HN recommender · 2018–2023
7 mo on HNBreak Me00 The MoVfuscator Turning mov into a soul crushing RE nightmare Christopher Domas
Adrian Crenshaw
6 HN recommender · 2017–2026
7 mo on HNA Talk Near the Future of Python (a.k.a., Dave live-codes a WebAssembly Interpreter)
David Beazley
7 HN recommender · 2019–2025
7 mo on HNMiguel de Icaza: Swift Godot: Fixing the Multi-million dollar mistake #GodotCon2023
Godot Engine
6 HN recommender · 2023–2026
6 mo on HNCppCon 2017: Matt Godbolt “What Has My Compiler Done for Me Lately? Unbolting the Compiler's Lid”
CppCon
7 HN recommender · 2018–2022
5 mo on HNCo-dfns Live Stream: Compiler Design and Architecture
Aaron Hsu (arcfide)
3 HN recommender · 2018–2025
5 mo on HNEric Bier Demonstrates Cedar
Computer History Museum
3 HN recommender · 2020–2025
5 comments from Hacker News
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
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
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
In the embedded video they show some of the code side by side and it is just a ton of if statements. ▶ this video
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