Anders Hejlsberg just dropped a talk that should make every

The headline grabber is the native port. After years of running on Node, the TypeScript compiler is being rewritten in Go. Not a binding layer, not a WASM shim — a ground-up reimplementation that keeps the exact same semantics while dropping cold-start latency from seconds to milliseconds. For anyone who's watched tsc --watch choke on a monorepo with 50k files, this isn't incremental. It's the difference between grabbing coffee while the type checker thinks and getting instant feedback on every keystroke.

Hejlsberg showed benchmarks where the new compiler processes the VS Code codebase (roughly 1.5M lines) in under a second. The old implementation needed 12-15 seconds. That's not optimization — that's a phase change. And because it's a clean-room rewrite with the same test suite, the migration path is essentially "swap the binary and keep working."

But the part that stuck with me wasn't the performance numbers. It was his answer when someone asked if AI coding agents make this compiler work obsolete. His take: AI writes code the way a junior writes code — fast, confident, and frequently wrong in ways that only type systems catch. The compiler isn't becoming less relevant; it's becoming the primary safety net for AI-generated code.

He framed it as a shift from "human writes, compiler checks" to "AI proposes, compiler verifies, human directs." The type system becomes the contract layer between non-deterministic generation and production requirements. That means stricter types, more exhaustive checking, and compiler features that surface semantic errors before they hit CI.

The Go port also unlocks something the JS implementation never could: true parallelism. The new compiler fans out type checking across all available cores without the worker-thread overhead that plagued earlier attempts. For large codebases, that's where the 10x actually materializes — not in single-file speed, but in scaling across the whole project graph.

There's a preview build floating around if you want to stress-test it against your own codebase. The team is explicit that it's not production-ready — edge cases around declaration emission and project references still need work — but the architecture is solid enough that they're targeting GA within the year.

What this means practically: if you're setting up a new TypeScript project today, you're building on a compiler that's about to get dramatically faster. If you're maintaining a legacy codebase, the upgrade path looks painless. And if you're betting on AI-assisted development, the type system just became your most valuable infrastructure investment.