Three dominant themes from the discussion
1. Performance leap in TypeScript 7
The release is being celebrated because the new compiler checks types orders of magnitude faster – a major win for large codebases and tooling.
“Codebase: 125.7 s → 10.6 s – 11.9× speed‑up” – tshaddox
“14× speed‑up over the 11× in VS Code, but Go is already good enough” – hoppp
“Congrats on the release – this is exactly what we’ve been waiting for” – pmpkg
2. Rewrite strategy: Go vs. Rust (and bug‑for‑bug translation)
Many commenters debate why the team chose Go for a near‑complete rewrite rather than Rust or a WASM‑based approach, pointing at team skill‑sets, concurrency needs, and integration concerns.
“They picked Go after meaningfully considering Rust (and others). It was detailed in the original blog post.” – paxys
“Rewriting the compiler in Go instead of just compiling the existing compiler to WASM … the article emphasizes speed, not much else.” – raddan
“Rust would take a lot longer … but Go is already good enough to make a huge difference.” – hoppp
3. Views on typing – enthusiasm, skepticism, and the Jevons‑paradox angle
The thread circles back to static vs. dynamic typing: some hail TypeScript’s type system as a breakthrough, others question its “most advanced” label and discuss how richer types can back‑fire (induced demand, Jevons paradox).
“Types are a safeguard, they rule out certain errors.” – egorfine
“The real story here is an incredible team that kept two separate codebases alive for the most advanced type system known to mankind.” – dimitropoulos
“When you increase the efficiency of a thing you thereby expand the set of things it can economically be used for … ‘a smaller slice of a much bigger pie is still more pie’.” – dimitropoulos
These three themes capture the core of the conversation: speed gains, the technical rationale behind the compiler rewrite, and broader attitudes toward typing and its trade‑offs.