Today's answer is: it all depends.
Although the signals themselves have been implemented, they are still in a developer preview phase, so be prepared for potential changes to the APIs without migration support from the Angular team.
The purpose of this developer preview is to gather feedback in order to finalize the API.
Another important detail is that signals are currently linked to the "old" change detection mechanisms. Updating the value of a signal will internally trigger the same code as markForCheck
. It's similar to how effect(() => {})
is connected to ApplicationRef.tick()
+ detectChanges()
.
As of now, there are no performance benefits to using signals. However, this may change in the future with the introduction of signal components.
If you're interested in learning how signals work, feel free to dive in and explore! But implementing them in an enterprise environment today may not be advisable.