Hello #angular people.
I have read the 🚥 and did write why I'm happy, and a bit on the Why and what (and then some)

https://github.com/SanderElias/Samples/tree/1ce26dcea5d4e3f0c3d93295c6de146229a7d327/Angular-Signals

Samples/Angular-Signals at 1ce26dcea5d4e3f0c3d93295c6de146229a7d327 · SanderElias/Samples

This is my repo where I do quick experiments and samples. - Samples/Angular-Signals at 1ce26dcea5d4e3f0c3d93295c6de146229a7d327 · SanderElias/Samples

GitHub
@sanderelias Btw hat I like the most about your example code `counter.value` instead of `counter()`. I personally really prefer the value

@sanderelias thank you for the insights about the Signals stuff!

Do you know about the existing Angular APIs which use RxJS. E.g. forms valueChanges, httpClient methods... will they be refactored to use Signals internally? Those APIs could still expose a subscribe method for backwards compatibility, I assume.

Or maybe there are plans to put a Signal API next to the existing Observable APIs?:

E.g.:

FormGroup.valueChanges
FormGroup.valueChangesSignal

#Angular

@sanderelias or maybe FormGroup.valueChanges can be Signal and Observable at the same time?

@spierala I'm unaware of any plans in this area.
Keep in mind that the primary focus will be replacing change detection.
I see forms internally using signals to visualize error state, or render updated values way before it's external API will be updated.

Long term, signals might be use to extend things where it makes sense.
I don't think any of the observables will be replaced.

@sanderelias if the Observable APIs will remain, then the Devs still have to learn RxJS.

I thought that was another main goal of the Signal story: make Angular easier to learn.

@spierala
Yes, it is. I highlight some of the reasonable in the article under learnability.

Also, digesting an observable is relatively simple. Building your own streams is where the hard part is. You can now use ANgular fine without learning that.
(IMHO your missing out, but not the point)

@sanderelias To be sure about the future of the RxJS APIs in Angular, I asked it on the Angular Signals discussion:

https://github.com/angular/angular/discussions/49090#discussioncomment-5120224

#Angular #RxJS

@spierala
I did put in an answer there. It gave me some more room as a toot!
@sanderelias @spierala Not going to add anything here of value but just wanted to say I’ve enjoyed this thread as although I haven’t done a deep dive into signals, yet, this feels like a great way to build knowledge to the upcoming ng16 release. Thank you.