วีดีโอ

thank you so much

My maan🎉🎉

You misspelled badass

@@nathanaelmayne5424 yes exactly!

Because he wants to be able to override the name at the component level, which you can't do with a computed.

@@wartab jeezzz... do you understand what's happening there? I'm not talking about what he wants - i understand what he wants. I'm talking about bug in his computed implementation. When options changes he want to reset index to -1. He don't want to reset index to -1 when index changes - but that's what will happen. Since computed depend on index and options then when he do select(idx: number) then it changes index to selected index and then computed is recalculated(because index changed and computed depends on index) and index is set back to -1 and that's not what he wants - that's bug in his implementation with computed.

They solve different issues. Signal is made to hold a value, while RxJS is not (because it's a stream). Angular signals make it easier to manage change detection

They ❤️ you too Lars! 😂🤣

Valid point Adrian! I think one challenge is that Angular was originally created as an internal tool for Google and shared with the open source community as an afterthought. Although the humans on the Angular team love the external Angular community (and we love them too), I don't think Google allocates resources for external documentation as much as we would like because the primary "clients" of the Angular team today are still internal Google teams. Fun fact! Did you know that the Angular docs already contain thousands of pages that need to be maintained and updated? It's a slippery slope! 😅 That's one reason why the Angular team has a family of volunteer Google Developer Experts, we are here to learn from the Angular team and help pass along consistent best practices to the community. That said, no one explains this stuff better than Alex Rickabaugh which is why we're so grateful when he makes time for us to have live discussions. Super helpful for us to ask him specific questions and repeat what he said back to him so he can elaborate and clarify when we're confused. Getting the architecture right becomes increasingly important at enterprise scale and affects performance, deadlines, cost, security and stability of the entire repo. Incidentally, enterprise scale is where Angular shines so we can assume that most teams committing to Angular are dealing with large applications. Creating samples or tutorials for every possible use case seems impossible even with help from GDEs or more budget for docs. With millions of external Angular developers, there would be many unique implementations and edge cases. This is true not only for Angular but for all open source projects, that's why Tech Stack Nation was created! 🤓 We host live office hours with an Angular GDE several times a week as well as frequent live discussions with the Angular team and other leading open source experts. Rather than creating demos for every possible scenario, you can come and talk to us about what you're working on. If we can't help you, well...we know who to ask! 😉🥰 #WeLearnTogether

hackmd.io/

Thanks Mo for the lovely comment! Be sure to say hello if you join our community, would be great to see you in our live calls! ~Bonnie 🥰

If you have writable signals which depend on another signal (e.g. a selected index from a list) you should think about nested signals. ⛄️

I also like to repeat back what I heard to make sure I heard it correctly, as you can see Alex often corrects me which is a big help to make sure I understand. Alex visits often so we will talk more about this, helps a lot for us to try out dev previews and meet him again for follow up questions. I see Lars also replied, he joined our study group after the last video so he was with us in the live call with Alex when this video was recorded, he's friendly and knowledgable about Angular so he's also a good guy to listen to. You're asking great questions too, hope we see you inside! #WeLearnTogether

@@techstacknation It's great to not only watch these videos "after the fact" but to be "live" at the event. Can recommend! 👍 I need to get used to actually talk to the "famous" people on the stream I "know" from TH-cam, because in the past I was just a viewer - distinguishing between "live" and "recording" needs practice. 🤣

I like that the community is using Google TH-cam for advertisement and lead magnets to sign up to the Tech Nation platform. It’s a way of owning and controlling your content away from Big Tech.

Thanks @@GuillermoArellano, you're exactly right! Our TH-cam videos are often just short clips of our ongoing discussions. There are more videos available exclusively for members of our free community, with the option to upgrade by joining our premium study group for immediate access to all our past and upcoming videos. Even better, joining our exclusive study group means that you can be in our live calls rather than watching later on youtube! 🥰

Full video is about an hour long and available for free without ads on TechStackNation.com!

I like that the community is using Google TH-cam for advertisement and lead magnets to sign up to the Tech Nation platform. It’s a way of owning and controlling your content away from Big Tech.

toObservable uses an effect under the hood. But what you have to keep in mind is, that you may not get all values that are set into that signal. You only get the last value whenever the effect is scheduled by the framework. When you really want to react to an event (like button click, input change etc.) you should use that as a source (through an observable, of course 😂).

@@larshanisch Agree! Speaking of Input, I think what would have been nice is if it could have behaved like FormControl (or BehaviorSubject for that matter) - from which you can either get the current value (snapshot) or the stream of changes, so that you can react granularly (e.g. make http requests), or even convert it to signal if you plan to further derive it. I know, you can do what I said with the old @Input and ngChanges, with an additional BehaviorSubject - but it would have been nicer to have a better (cleaner, more uniform) integration.

@@adrianspiridon old @Input only fires once in ngOnChanges, because "expression changed after check" 😄 I think of signals/toObservable as "automatic debounce". And I haven't had a situation where I got bitten by this. After all the rendering of a template is also an effect, so the bound signals are only read at specific timings. They are no events on every level... Most of the times I start requests either on clicks/submits or valueChanges of forms. So I'm fine!

Hmm, interesting. In most of the cases I run into, signals changing should not be the trigger to fetch data, instead that should be at the end of the stream created by an event (if we use unidirectional state patterns, which we should). What should trigger the http call is a user action, a route change, or some other event. So the event is the trigger, then process that action doing whatever you need, and at the end of it, change the state (similar to flux/redux pattern). Of course we will run in the situation you describe for example when a component input changes, then we need to react to that change, which is triggered by a signal change.. In those cases I use ngOnChanges, but in the Standalone Component RFC they say that they will remove this hook and instead recommend to use effect 🤷‍♂ I guess we are in the middle of a paradigm change and things need to settle down...

@@codeSurvivor You're right, we're in the middle of discovering new patterns with all these things. I really like using signals inside the template, but I wonder if implementing inputs as signals was the right way - maybe they should've been more like observables as the new output are. If I need to react to changes on inputs (and we all should do) then I just use toObservable (which uses an effect under the hood). After all signals have the advantage that they are in sync (if multiple inputs change at the "same" time). If I need to combine them into a stream, I first "computed" them into the thing I want to stream (so I'm glitch-free) and after that I use toObservable, so I don't have to use combineLatest or similar.

Yep, I agree. The terminology alone is confusing. We're talking about something that is meant to be "computed"(), e.g. it's calculated, based on other inputs, but here it's not always computed, because we're sometimes setting parts of it manually. I don't think that'll ever feel right to me :D

@@delie32 This means linkedSignals is the angular teams final solution?

don't think they will remove the option to set signal inside effect. probably they'll just remove the necessity of putting an {allowsignalWrite: true} option. they will make it as default if im not wrong

The thing is that those subscriptions are not the same as rxjs subscriptions, in the sense that you have to make sure to unsubsribe from them. When the computed runs, the signal previously created inside it is automatically 'disposed', removing it as 'dependecy' of any reactivity depending on it.

Excellent question zzing! If you'd like to create a quick stackblitz and post a link here, I can show it to Alex next time he stops by or, even better, you can join us on TechStackNation.com and ask him yourself! #YouCanSitWithUs 🥰

Thanks for the feedback Mr. Ilya, we've uploaded it again with a higher resolution 👉 th-cam.com/video/7BAIyJ8O2x4/w-d-xo.html 🥰

Though using `effect` under the hood you could use `toObservable` together with `outputFromObservable` here with: isEven = outputFromObservable(toObservable(this.number));