Angular introduced Signals1 in Angular 17. You can find a mention of it in the release notes3 along with other fantastic goodies. From what I hear it's a big thing that solves some of the problems with updating two-way data-bindings without having to go through the entire tree of components and examining all the state (wich zone.js used to do.)
However, it's not a one-size-fits-all. Observables are still highly relevant, it's just that sometimes you use Signals and sometimes you use Observables2.
From what I gather, Signals can be used for highly synchronous code and one of those is to use them in the UI. Where Observables are convenient if the value is not immediately available (so time-based) like with REST calls.
You can learn about it all and try it out at [4], apparently.
There's plenty of youtube videos out there that introduce the concept too, apparently.
References
- [1] Angular - Angular Signals
- https://angular.dev/guide/signals
- [2] Medium - Angular Signals: Best Practices
- https://medium.com/@eugeniyoz/angular-signals-best-practices-9ac837ab1cec
- [3] Angular Blog - Introducing Angular v17
- https://blog.angular.dev/introducing-angular-v17-4d7033312e4b
- [4] Angular Home
- https://angular.dev/
