Thank you very much for your valuable content , but i need to ask a question regarding the computed and specially for the example you used what the different between calling usersTotal() in the html template and calling users().length directly ? is there any advantage of using computed in this case ? and thanks again
In this case not really. computed is some logic that you want to compute. Reading length has no logic so you don't need computed. It is also a good place for logic which you don't want to write in html.
For me,signal just looks like useState and useEffect in React,with more functionalities like mutable and compute.But,in my opinion change detection will easier and quicker by signals.
The video was very clear! I just didn't understand how effect works: how does it know to trigger when title is changed and not when users does? Does it trigger every time any signal change?
As for now effect is called if any signal changes. I would like to see some api to trigger it only for specific signal similar to dependencies of useEffect in react
Effects will only run if any of their dependencies change, from the docs: Effects always run at least once. When an effect runs, it tracks any signal value reads. Whenever any of these signal values change, the effect runs again. Similar to computed signals, effects keep track of their dependencies dynamically, and only track signals which were read in the most recent execution.
Thank you! Amazing video! What is the difference between update() and mutate()? Does update() trigger change detection in the current component while mutate() does not?
Sorry for out of context question, in ngrx can and should i update state from the backend service without any actions dispatched from from user (commercial platform) Thanks in advance
Signals are not just easier to grasp, than RXJS, but they are also closer to what's actually happening under the hood. - the fact alone, that your effect methods now can run sync instead of async, without frankensteining your ngOnChange method, is a feature in itself
At the moment I just don't really like the idea of making async things sync just by using toSignal with an arbitrary initial value. Sometimes, effects don't work as desired/expected when this arbitrary value comes in as the first value before the database value. For example, my effect needed to calculate a default value for a form field when it was null, so I did it in an effect, but the problem was this arbitrary value came in before the db value and so the wrong value was assigned to the form field. In my opinion, it is better to just wait for the database value, which means using rxjs instead of a signal. In my opinion it is better to use rxjs for async stuff, and use signals for sync stuff if you want, but for me I find it simpler to just use rxjs for everything.
I really don't like the esthetics of signals. Code separation which ngrx offers make code base really clean. I hope angular team comes up with something which makes code looks cleaner.
Hi, exists something like a benchmark? I learned that we should not call functions in Angular because it will make the app significantly slower. But with the signal you added a function to the view. How fast is it compared to older approaches?
Calling signals is not like calling a function, it's perfectly safe to do. Calling a function is discouraged due to Angular's change detection mechanism, but signals won't trigger change detection like functions would in the template.
@@MonsterlessonsAcademy we have in rxjs multicast operators (BehaviorSubject - ReplySubject - AsyncSubject, EventEmitter) son we can achieve exactly the saqme as Signals
@@MonsterlessonsAcademy I disagree - they both do state management, they both can interconnect components, and they both stream data the same way. In fact they are really no different than a behavior subject.
![Lp. Сердце Вселенной #30 ДВА В ОДНОМ [Один человек]• Майнкрафт](http://i.ytimg.com/vi/nrXy15orKhY/mqdefault.jpg)
WATCH NEXT: Angular Interview Questions and Answers - Dominate Your Next Interview - ua-cam.com/video/5A_YKlVWMPo/v-deo.htmlsi=2DCn7yspEAAJ2H6l
Thank you very much for your valuable content , but i need to ask a question regarding the computed and specially for the example you used
what the different between calling usersTotal() in the html template and calling users().length directly ? is there any advantage of using computed in this case ? and thanks again
In this case not really. computed is some logic that you want to compute. Reading length has no logic so you don't need computed. It is also a good place for logic which you don't want to write in html.
For me,signal just looks like useState and useEffect in React,with more functionalities like mutable and compute.But,in my opinion change detection will easier and quicker by signals.
I agree. Looks like copy pasting ideas from React
They are copying and pasting from solid.js@@MonsterlessonsAcademy
I always look forward to your content. Any plans on getting in testing in Angular with Jest for example?
Thank you for the idea. I will add it to the list of future videos.
The video was very clear! I just didn't understand how effect works: how does it know to trigger when title is changed and not when users does? Does it trigger every time any signal change?
As for now effect is called if any signal changes. I would like to see some api to trigger it only for specific signal similar to dependencies of useEffect in react
@@MonsterlessonsAcademy wow that's very weird...
@@MonsterlessonsAcademy Oh I see, I hope they give us a way to specify which effect should trigger or we have to make some custom shenanigans 😅
Effects will only run if any of their dependencies change, from the docs:
Effects always run at least once. When an effect runs, it tracks any signal value reads. Whenever any of these signal values change, the effect runs again. Similar to computed signals, effects keep track of their dependencies dynamically, and only track signals which were read in the most recent execution.
Thank you! Amazing video! What is the difference between update() and mutate()? Does update() trigger change detection in the current component while mutate() does not?
Actually, I can't seem to find mutate() in the Angular docs anywhere. I can only find update(). Did they remove mutate()?
You are right. They removed mutate (which is awesome)
Sorry for out of context question, in ngrx can and should i update state from the backend service without any actions dispatched from from user (commercial platform)
Thanks in advance
is it better in general to use signals instead of variables that are binded to UI for example?
Yes it is better.
Hello,
Thanks for your videos.
I have a question, are you from Germany?
where are you from?
Hi, originaly from Ukraine but last 8 years living in Hamburg.
Helpful and concise thank u!
Glad it was helpful!
So signals need only for not enter in life cycles, they are not accesible from other components like subjects?
You can put them in service and reuse everywhere
Signals are not just easier to grasp, than RXJS, but they are also closer to what's actually happening under the hood. - the fact alone, that your effect methods now can run sync instead of async, without frankensteining your ngOnChange method, is a feature in itself
Yeap
At the moment I just don't really like the idea of making async things sync just by using toSignal with an arbitrary initial value. Sometimes, effects don't work as desired/expected when this arbitrary value comes in as the first value before the database value. For example, my effect needed to calculate a default value for a form field when it was null, so I did it in an effect, but the problem was this arbitrary value came in before the db value and so the wrong value was assigned to the form field. In my opinion, it is better to just wait for the database value, which means using rxjs instead of a signal. In my opinion it is better to use rxjs for async stuff, and use signals for sync stuff if you want, but for me I find it simpler to just use rxjs for everything.
I really don't like the esthetics of signals. Code separation which ngrx offers make code base really clean. I hope angular team comes up with something which makes code looks cleaner.
You can continue use ngrx and they will use signals underneath.
you are comparing apples with oranges
hello, what text editor are you using?
love the channel
It's Vim here is my video about it ua-cam.com/video/YrLiugDhCuk/v-deo.html
Great video! Thanks
You're welcome!
Why do we need [value]="title()" in html if we change signal in event function?
Because we need to render a value in the input
I don't get it. Why can't we just use the ngModel directive with events? It doesn't make sense to use a variable like title as a method call.
ngModel works through change detection cycle and signals not. Change detection cycle is slow on big apps and signals not.
Hi, I am a bit confused, to me it looks like ngModel, whats the difference?
It doesn't trigger Angular change detection cycle. It is extremely fast in big apps
Hi, exists something like a benchmark? I learned that we should not call functions in Angular because it will make the app significantly slower. But with the signal you added a function to the view. How fast is it compared to older approaches?
I didn't see any benchmarks or real app comparisons yet.
Calling signals is not like calling a function, it's perfectly safe to do. Calling a function is discouraged due to Angular's change detection mechanism, but signals won't trigger change detection like functions would in the template.
@@baluditor thank you, I had a chance to look into angular 16 now too and I think you are right.
Excellent explanation
Glad you like it!
@@MonsterlessonsAcademy we have in rxjs multicast operators (BehaviorSubject - ReplySubject -
AsyncSubject, EventEmitter) son we can achieve exactly the saqme as Signals
Amazing content!
Glad you think so!
Very helpful
Glad you think so!
Can we cancel a signal that has been created?
Why do you need to do that? It is not a subscription. It's the same like creating a subject. I doesn't cause performance problems.
@@MonsterlessonsAcademywhy not just use the BehaviorSubject instead of signal? is there some other cases of signal usage that I’m missing?
Wow.
Hey, really likeing your paid course my guy.
Glad to hear that!
Target with a g as in girl not j
I still think Rxjs is better than signals.
They are different
@@MonsterlessonsAcademy I disagree - they both do state management, they both can interconnect components, and they both stream data the same way. In fact they are really no different than a behavior subject.
they are copying from react and vue lol
Yeap a bit
@effectssss