TypeScript is being rewritten in Go to deliver substantial performance gains, while Angular's latest Q&A session revealed that Streaming SSR is on the roadmap but lacks prioritization. Additionally, both ng-conf and Angular Connect are set to return.
TypeScript's migration to Go
Because the Angular compiler depends directly on the TypeScript compiler, any modifications to TypeScript ripple through to Angular. Anders Hejlsberg, who leads TypeScript's architecture at Microsoft, has revealed that the language is undergoing a port to Go.
A 10x Faster TypeScript - TypeScript
Embarking on a native port of the existing TypeScript compiler and toolset to achieve a 10x performance speed-up.
devblogs.microsoft.com
The TypeScript compiler was originally authored in TypeScript itself — a classic case of eating your own dog food. While developers won't need to learn Go, they will see a considerable speed advantage. Early benchmarks indicate up to a 10x improvement in performance alongside a 50% reduction in memory consumption.
This shift aligns with a wider pattern in the developer tooling space: more projects are adopting languages that compile to native binaries for enhanced efficiency. Notable examples include esbuild, Rolldown, and Rspack. Native code is pre-compiled and optimized for specific architectures. Unlike JavaScript, it doesn't require interpretation or runtime compilation—it's execution-ready immediately.
Another benefit is true concurrency, a capability JavaScript doesn't offer.
Furthermore, Go's syntax bears a strong resemblance to JavaScript, simplifying the porting process considerably.
For everyday developers, the payoff is a noticeably faster TypeScript experience — more responsive editors, reduced build durations, and the possibility of richer language features that were previously held back by performance limits.
Hejlsberg also noted that the revamped compiler could enable immediate validation of AI-generated code. It could flag errors in suggestions from assistants like Copilot or ChatGPT in real time, making AI-supported development workflows more dependable and productive.
A fully operational compiler is targeted for release by year's end, although certain capabilities — such as JSDocs, project references, and build mode — will be missing at launch. Given Angular's heavy reliance on TypeScript, the framework may require additional time to fully adopt the new compiler.
Angular Q&A: SSR & Incremental Hydration
This week's Angular Stream featured Jessica Janiuk, who demonstrated SSR combined with Incremental Hydration and addressed pressing audience questions.
The most notable insight? Streaming SSR is indeed planned, though its timeline hinges on how it's prioritized against other work.
The conversation also touched on whether defer and hydration should consistently be paired. The consensus: incremental hydration targets loading performance. After the app is running, defer becomes the primary tool. Additionally, incremental hydration requires a server operating in the background, while apps that rely solely on defer can be served from static file hosts.
A significant portion of the stream involved debugging, so a useful reminder emerged: disable HMR during development if you want to observe defer's complete behavior.
https://www.youtube.com/live/J7cQ-_dZ0w8
Ng-Conf & Angular Connect
Elsewhere, two major Angular conferences have been scheduled for later this year. ng-conf is staging another event, and Angular Connect — historically among the largest Angular gatherings — is returning after its hiatus.