A 10x faster TypeScript
Microsoft Developer2 HN recommenders · recommended in 2 months, 2025-2025
608K views · 1 year ago · talk · dated
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.
1:01:31TypeScript is being ported to Go | interview with Anders Hejlsberg
Michigan TypeScript
102K views • 1 year ago
29:47The Truth about Rust/WebAssembly Performance
Greg Johnston
218K views • 3 years ago
56:23Speed Up Your JavaScript
Google TechTalks
136K views • 17 years ago
35:42Progressive Performance (Chrome Dev Summit 2016)
Chrome for Developers
34K views • 10 years ago
34:10Anders Hejlsberg on Modern Compiler Construction
Kasper
25K views • 9 years ago
1:00:34High Performance Web Sites and YSlow
Google TechTalks
90K views • 18 years ago
43:14Anders Hejlsberg and Lars Bak: TypeScript, JavaScript, and Dart
DartlangTV
14K views • 13 years ago
12:01React without memo
React Conf
150K views • 4 years ago
59:31ClojureScript in the Age of TypeScript — David Nolen
ChariotSolutions
29K views • 5 years ago
45:49Breaking the 1000ms Time to Glass Mobile Barrier
InfoQ
104K views • 13 years ago
51:12Google I/O 2011: Writing Web Apps in Go
Google for Developers
135K views • 15 years ago
1:32:47Data-Oriented Demo: SOA, composition
Jonathan Blow
201K views • 11 years ago
22:51GopherCon 2015: Go GC: Solving the Latency Problem - Rick Hudson
Gopher Academy
22K views • 11 years ago
45:05Servo Architecture: Safety and Performance
linux conf au 2017 - Hobart, Australia
12K views • 9 years ago
27:43Bringing SIMD to the Web via Dart
InfoQ
11K views • 13 years ago
1:02:44Chris Seaton @ VMSS16: JRuby+Truffle: Why it’s Important to Optimise the Tricky Parts
softdevteamuk
5K views • 10 years ago
1:04:48"Performance (Really) Matters" with Emery Berger
Association for Computing Machinery (ACM)
7K views • 6 years ago
34:55"Outperforming Imperative with Pure Functional Languages" by Richard Feldman
Strange Loop Conference
98K views • 5 years ago
33:52Nordic.js 2014 • Douglas Crockford - The Better Parts
Nordic.js
73K views • 12 years ago
47:34RailsConf 2011: Aaron Patterson, "Double Dream Hands: So Intense!"
O'Reilly
26K views • 15 years ago
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
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
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
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
In the embedded video they show some of the code side by side and it is just a ton of if statements. ▶ this video