Signals could one day be built directly into JavaScript itself. Additional specifics about the Angular/Wiz collaboration came to light, and Alan Agius appeared as a guest on the "Adventures in Angular" show.
Signals as TC39 Proposal
It’s common to treat Signals as framework-specific functionality, but that perspective could shift. A TC39 proposal is currently in progress, potentially paving the way for Signals to become part of the JavaScript standard. Such a move would deliver several benefits.
Standardization could simplify cross-framework migration, encourage tooling to adapt around them, and, once native browser support lands, lead to smaller bundles and better performance.
Every major framework has contributed to this initiative, which is still nascent and guided by Rob Eisenberg.
A key consideration is whether Angular’s existing syntax will need an overhaul to accommodate this change.
That’s probably not the case. Signals are designed mainly for framework authors, who will integrate them into their own systems and connect their rendering logic.
For those curious, a polyfill is already accessible.
tc39
/
proposal-signals
A proposal to add signals to JavaScript.
🚦 JavaScript Signals standard proposal🚦
Stage 1 (explanation)
TC39 proposal champions: Daniel Ehrenberg, Yehuda Katz, Jatin Ramanathan, Shay Lewis, Kristen Hewell Garrett, Dominic Gannaway, Preston Sego, Milo M, Rob Eisenberg
Original authors: Rob Eisenberg and Daniel Ehrenberg
This document describes an early common direction for signals in JavaScript, similar to the Promises/A+ effort which preceded the Promises standardized by TC39 in ES2015. Try it for yourself, using a polyfill.
Similarly to Promises/A+, this effort focuses on aligning the JavaScript ecosystem. If this alignment is successful, then a standard could emerge, based on that experience. Several framework authors are collaborating here on a common model which could back their reactivity core. The current draft is based on design input from the authors/maintainers of Angular, Bubble, Ember, FAST, MobX, Preact, Qwik, RxJS, Solid, Starbeam, Svelte, Vue, Wiz…
eisenbergeffect.Medium
Angular & Wiz
In the prior episode, we touched on how Angular is teaming up with Wiz, Google's internal framework known for its speed.
Minko Gechev, Angular's product lead, has now shared a blog post that spells out the specifics. The overarching goal is to combine the two frameworks into one.
This entails bringing Wiz's capabilities into Angular gradually — a process that's already becoming clear through the recent strides we've seen in server-side rendering.
Angular and Wiz Are Better Together | by Angular | Angular Blog
Authors: Jatin Ramanathan, Minko Gechev
blog.angular.dev
Alan Agius at "Adventures in Angular"
On the Adventures in Angular podcast, the Angular team's Alan Agius made an appearance. His primary responsibility is the Angular CLI, and public speaking engagements from him are rare.
The conversation covered how Nx and the Angular CLI handle libraries differently, the tooling for i18n, and module boundaries along with strategies for their enforcement.
1x
initializing...
×
Paul Gschwendtner on output()
Another Angular team member, Paul Gschwendtner, shared his own write-up on the output() function, which became available with Angular 17.3.
Meet Angular’s new output() API. Angular v17.3 introduces the improved… | by Paul Gschwendtner | Angular Blog
Angular v17.3 introduces the improved API for declaring outputs as a developer preview.
blog.angular.dev