TypeScript is moving to Go for major speed boosts, while Angular’s Q&A confirmed Streaming is planned but not prioritized. ng-conf and Angular Connect are also making a comeback.
TypeScript's port to Go
The Angular compiler is built on top of the TypeScript compiler, so any change to TypeScript has a direct effect on Angular. Anders Hejlsberg, the lead architect of TypeScript at Microsoft, announced that TypeScript is being ported 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 written in TypeScript itself - kind of eating your own dog food. This doesn’t mean developers need to learn Go, but it does mean a significant performance boost. Initial benchmarks show up to a 10x improvement in speed and half the memory usage.
This move follows a broader trend in tooling: more projects are shifting to languages that compile to native code for better performance. Examples include esbuild, Rolldown, and Rspack. Native code means compiled code and optimized for the target architecture. Unlike JavaScript, it doesn’t need to be interpreted and compiled at runtime—it’s ready to go from the start.
It also enables real concurrency, something JavaScript lacks.
On top of that, Go is syntactically similar to JavaScript, which makes porting much easier.
For developers, this means a faster TypeScript experience - snappier editors, quicker build times, and the potential for more powerful language features that were previously constrained by performance.
Anders Hejlsberg mentioned that the new TypeScript compiler could enable real-time validation of AI-generated code. It wouldinstantly flag errors in suggestions from tools like Copilot or ChatGPT. This makes AI-assisted coding more reliable and efficient.
A fully functional compiler is expected by the end of the year, though some features - like JSDocs, project references, and build mode - won’t be ready initially. And since Angular relies heavily on TypeScript, it may take longer for the framework to fully integrate with the new compiler.
Angular Q&A: SSR & Incremental Hydration
This week’s Angular Stream featured Jessica Janiuk, who walked through SSR with Incremental Hydration and answered key questions.
One of the biggest takeaways? Streaming SSR is planned, but its release depends on priority.
There was also discussion on whether defer and hydration should always be used together. In short, we should remember that incremental hydration is for loading performance. Once the application is up and running, defer is the way to go. Incremental hydration also depends on a server running in the background, whereas applications using only defer can be hosted by static web servers.
During the Q&A, some heavy debugging was going on. So here’s a reminder: Disable HMR in dev mode if you want to analyze the full behavior of defer.
https://www.youtube.com/live/J7cQ-_dZ0w8
Ng-Conf & Angular Connect
In other news, two major Angular conferences have been confirmed for later this year. ng-conf is happening again, and Angular Connect - once one of the largest Angular events - is making a comeback.
Top comments (2)
Thanks a lot!