iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Bytes #375, published March 13, 2025, centered on Microsoft’s plan to port TypeScript’s compiler and tooling to Go. The project is no longer just a proposal: Microsoft announced TypeScript 7.0 as available on July 8, 2026, and described it as the native Go port. The performance figures are promising, but they are Microsoft-reported benchmark results—not a guarantee that every codebase will build or feel faster by the same amount.
What “King Hejlsberg’s Decree” refers to
The title story in Bytes #375 was about Anders Hejlsberg, TypeScript’s technical fellow, and Microsoft’s announcement of a native implementation of the TypeScript compiler and tooling in Go. Hejlsberg announced the next steps on March 11, 2025, describing the effort as an attempt to improve TypeScript performance, particularly for very large projects.
The newsletter’s title is playful framing, not a claim that Hejlsberg issued a decree or that TypeScript was being replaced. The subject was an engineering change to the compiler and language-service implementation. The issue also touched on JavaScript engines and code quality, but those were supporting themes rather than the meaning of its headline.
Free tools Windows power users keep installed
One-click scans. No signup required.
How the project changed after the issue
In March 2025, the Go port was an announced effort with an early benchmark result. Microsoft later announced TypeScript 7.0 availability on July 8, 2026, identifying it as the native Go port. That makes the original story a report on a project that has since reached an announced release, rather than a description of the finished state of TypeScript at the time Bytes #375 appeared.
#1 Best Overall
What Microsoft’s speed figures do—and do not—show
| Announcement | Reported result | How to interpret it |
|---|---|---|
| March 11, 2025 | 10.4× speedup on Microsoft’s VS Code build benchmark | A result for that benchmark and workload, not a promise for every TypeScript project. |
| July 8, 2026 | Typically 8× to 12× faster full builds in Microsoft’s testing | Microsoft’s reported typical range; it is not an independently verified result or a guarantee for an individual project. |
The two announcements describe different benchmark contexts, so their numbers should not be treated as interchangeable measurements or as evidence that the performance changed from 10.4× to a lower or higher figure. Build time can depend on project size and composition, dependencies, configuration, and the work being measured. Neither reported figure establishes how much faster a particular repository will be.
Why Microsoft chose Go
Bytes described the choice as specific to Microsoft’s workload. Go provides native compilation across platforms, control over data layout, support for cyclic data structures, automatic memory management, and concurrency support. Those properties help explain why Go was suitable for the team’s implementation; they do not establish that Go is categorically the best language for building compilers. The issue’s comparison with Rust and C++ is best read as engineering context, not a universal ranking.
Rank #2
- TypeScript implements a superset of syntax for strictly typed development, facilitating deep static analysis and enhanced development environment integration. The compiler translates source into standard script formats, ensuring parity across any runtime.
- TypeScript is ideal for front-end developers, full-stack engineers, and software architects who build large-scale web applications. It serves those looking to improve code excellence, reduce bugs through static checking, and maintain complex projects more.
- Lightweight, Classic fit, Double-needle sleeve and bottom hem
What TypeScript users should take from the story
The clearest takeaway is that Microsoft pursued a native compiler and tooling implementation to improve performance, and later announced TypeScript 7.0 availability with substantial speedups in its own testing. For an individual team, the useful question is not whether a headline multiplier applies universally, but how the new compiler behaves on its own workload.
- Compare build times on the same named project and workload, using consistent conditions.
- Check language-service and editor responsiveness separately from full-build time; they are different parts of the developer experience.
- Review compatibility and migration requirements, especially if the project relies on specific compiler features or APIs.
- Treat Microsoft’s figures as reported results, and avoid assuming they predict a project-specific outcome.
Bytes #375 remains a useful snapshot of the announcement and its rationale. Read with the later TypeScript 7.0 announcement in view, its central story is the transition from a proposed Go port with an early benchmark to a released compiler generation accompanied by Microsoft’s broader performance claims.
Quick Recap
Best Value
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
