ANGULARarchitects.io - Michael Egger-Zikes
Since the release of Angular 17, the first part of the Signals implementation is now production-ready. Those APIs offer an additional concept besides RxJS to handle reactivity and influence the framework in many areas. Signals will lead to a different more fine-grained and more performant way of processing the Change Detection to update the view. All of this is added to be backward-compatible.
While using Signals feels simpler and more intuitive than RxJS subscription management, it isn't likely to replace RxJS in all areas. Since Signals are easy to work with, many developers are surprised how the “Magic of Angular Signals” is implemented behind the covers and why it is possible that computed values, effects, and Component Templates reprocess as dependent Signals change.
This talk will give insights into how Signals are implemented to make sure that they update correctly and no intermediate processing results are sent out.