Change detection and Angular signals in Angular v16
ฝัง
- เผยแพร่เมื่อ 6 พ.ค. 2023
- Learn about the exciting news regarding Angular signals, and how these features help build better apps. Find out how to get started with Angular signals now that it’s available for developer preview.
Learn more about Angular v16 → goo.gle/angular-v16
Angular signals → goo.gle/angular-signals
Watch more videos about Angular v16 → goo.gle/Angularv16
Subscribe to Angular → goo.gle/Angular
#Angular - บันเทิง
![เกิดใหม่ทั้งทีก็เป็นสไลม์ไปซะแล้ว ซีซั่น 3 - ตอนที่ 57 [ซับไทย]](http://i.ytimg.com/vi/pNhft3YZFRE/mqdefault.jpg)
Learn more about Angular v16 → goo.gle/angular-v16
Angular signals → goo.gle/angular-singals
angular signals link not working
Angular signals link doesn't work?
Simple video but all I needed to get bopping with signals. Thank u!
Love the naming; super intuitive!
Great stuff, will update my applications as soon as it is production ready!
Yes! What's a problem this syntax solves for you?
@@Angular i imagine using far fewer async pipes thanks to signals
Thx for the info. Looking forward to using Signals. Glad Angular is moving in this direction.
Interesting.
Thank you.
Please explain real time implementation of signals and computed with their pros & cons.
Good ,Thanks.
What are the alternatives to mimic this approach in Angular 15?
Angular team, how can i upgrade my angular application from version 12 to v.15, in between i facing lots of dependency conflicts ?
FYI: Signals link not working.
Sorry, try this out: angular.io/guide/signals
So interesting
I'm not sure if I understand it correctly: Is the goal to go away from the "classic" 2-way-binding approach? That would be a bummer
yes, it's going to change: inputs and outputs will be implemented with signals, not with decorators; but it will be backwards compatible so old code won't break when you update Angular.
@@rickelmonoggin thanks for your answer, but I meant more about in general. If we still with have two-way-binding or a React-like concept for Angular as whole.
spending time learning ngrx, rxjs , reactive forms,...for nothing, thanks angular
Signals will be interoperable with RxJS and we haven't finalized the Reactive Forms story just yet. We're also working with library authors on this stuff, too! So your hard work isn't all for nothing :)
Somehow, I’m more comfortable with rxjs than signals, only feature I didn’t like in ng is depending on ngOnchange instead reactive inputs.
signal component will solve this problem
sweet
How to call a function on signal change.
Effect is one function, how we know which signal changed thatswhy effect called.
"When the value of the signal they USE change"
When you defined function effect( () => { signal1(); signal2(); } ) then effect( () => { signal1(); signal3(); } ) - so when signal2 is updated, then the first effect function will be called, when signal3 is updated then the second effect will be called. When signal1 is updated - then both effect will be called. I hope I got it right :)
Wrong link: singals -> signals
Almost like mobx
the core concept is derived from the React useState and useEffect hook to update the DOM.
not the concept but DX,
under the hood there is no VDOM or working loop, it uses shadow dom and render pipelines ( in theory this can be faster than VDOM ), signals are inspired more by Solid than React
hahaha don't push the react concept on Angular. It will never suffice. Angular doesnt have a VDom. REACT is not REACTIVE. REACT has a false reactivity concept.
Did someone give angular the apple 'new product' script ? like damn
takeUntilDestroy and signals - when you use own framework and tired to type all that spaghetti (me too) 😄
that's what I call user friendly! Guys you are brilliant!
ReactJS is not reactive.
Why so many major changes all the time? 1st from Angular Js to Angular 2 , which shook confidence of consumer who put money in Angular Js. Now we will have libraries with old way and signal way. Doesn't boost my confidence with these Fancy stuffs .
This is not breaking change, this is just optional feature which you can use for your benefits. But it's also perfectly fine to do as you are used to :)
@@Mego4884 I agree but I think it would be more confusing for new devs to understand both approach. Angular already requires steep learning curve. I have been working on angular since 2016 , and I feel that it is gonna solve important problem but will bring more complexity with 2 diff approaches. All libs will start releasing 2 versions now. That's what I don't like
It’s the angular way, it gets frustrating. Looks like a load of extra boiler plate to add more dev work where I thought Angular should be letting us code and sort out the updates to UI behind the scenes 🙄
They take this new path without asking the community
@@mugatu2017 they did a whole RFC about it to get community feedback
This video format is horrible it takes 2 minutes to get to the 1 minute point.
2:00 skip to here guys
angular is digging his own grave
Why do you think that?
Yea, I'd love to know that as well. Seems like a great change and no one forces you to use signals. If you dislike them just stick to rxjs
I think it's a great addition. Forever people complained about the Zone.js change detection being slow, inefficient, etc. I think Signals is their way to resolve that problem.
It is a good solution and a pretty nice feature. The thing our friend here meant was that Angular core code base became so huge, that it’s almost impossible for a new developer to learn it all 😕
That’s why breaking changes should not be avoided.
Fear of change hurts way more.