Microsoft stages TypeScript native port

This is the kind of compiler rewrite that matters if you spend all day inside huge codebases. The upside is real performance and smoother editor workflows; the tradeoff is that compatibility and parity now have to prove themselves in public.

• –The project is not just a code dump; it exposes a status matrix so developers can see exactly what is done, partial, or not ready
• –Microsoft is optimizing for a low-friction migration path: preserve TypeScript 6.0 semantics, ship a preview package, then fold it back into the main TypeScript repo later
• –The Go choice signals a practical bet on native speed and shared-memory parallelism rather than a greenfield rewrite
• –The biggest near-term value is for large monorepos where type-checking latency and watch-mode responsiveness are the daily pain points
• –Because this is staged as open source early, the community can surface edge cases before the eventual TypeScript 7 rollout hardens the defaults