signals for components and templates and observables for http requests is a great way of defining the use cases for both. not having to use async pipe and subscribe is a godsend.

@deborah_kurata

5 ай бұрын

Yep! Agreed. Looking forward to more exciting signal features!

Thanks for your videos about signals, I watched all Signal playlist and I didn't hear about Signal effects is in practice, I hope I'll be first to see about effects from your channel 😊 if you are planning to publish video about that Thanks again. 😊

@deborah_kurata

7 ай бұрын

There are some issues with effects, specifically about how they are scheduled, that the Angular team is still working on. So the effects feature is still in "developer preview" while most of the other signal features are now in a "stable" state.

Amazing Deborah. Subscribed!

@deborah_kurata

7 ай бұрын

Thank you! 😊

Hey! 👋 I'm a dedicated follower of your content and absolutely love the unique perspective you bring to the platform. I'm passionate about what you do and believe I could contribute significantly as your channel manager. With my computer skills, I'm confident in my ability to help elevate your channel even further. Let's chat about the exciting possibilities - I'm not just a fan; I'm ready to be an integral part of your success story!

@deborah_kurata

6 ай бұрын

Thank you so much for your offer. I'm not in the market for a channel manager right now.

Hello! Mam, can you please discuss how the signal will improve the change detection. How it actually notify Angular to run the reconciliation process. Thank You so much :)

@deborah_kurata

7 ай бұрын

With Angular v17, the improved change detection is not yet fully there. The Angular team is still working on it. I'm planning to do a video as soon as the new functionality is in place. What currently works is the OnPush change detection strategy. When a signal is read in a template, that signals is "registered" to be tracked. When that signal is changed, Angular marks the component as "dirty" and the value is updated the next time change detection runs. See the Angular documentation for more information: angular.io/guide/signals#reading-signals-in-onpush-components

i was trying to figure out a good dividing line for where to use what and that makes a lot of sense. i like rxjs (now that i understand it) and would still like to use it. processing data seems like the best application and using signals to update the ui is much better

@deborah_kurata

7 ай бұрын

Sounds like a great approach!

Hello thank you for this wonderful video I have a question regarding signals, if the goal of signals is to use signals inside html template and avoid using normal variables, what about when we have a signal of a complex object with a lot of properties to bind with the html template, using only this signal object to access properties inside the html is like not using signals anymore, one solution is to compute every property into a signal which will generate a lot of additional work and memory allocations I hope Angular team comes up with some sort of solution.

Thank you very much for all your clear explanations, I enjoy your videos very much... Can you please tell if the rxjs interop package is already stable in angular 17? Is it still not the time to implement Signals with rxjs interop in my projects?

@deborah_kurata

7 ай бұрын

Glad the videos have been useful! The RxJS interop package is still in developer preview. (As per this: angular.io/guide/rxjs-interop) I've been using them in my services, so they are fairly encapsulated. It wouldn't be too difficult in my code to modify them if the API changed. You *could* using RxJS Interop in your project now, knowing the API could change. Or you could wait for them to be marked as "stable". You'd need to weight your benefits vs risks.

Can you describe the differences and use cases for using Signals vs Ngrx? I learned Ngrx from your course and wondering how to know which tool should be used.

@deborah_kurata

6 ай бұрын

The latest version of NgRx uses signals: dev.to/ngrx/announcing-ngrx-v17-introducing-ngrx-signals-operators-performance-improvements-workshops-and-more-55e4 Right now, signals provide several key functions: - The ability to have computed properties that automatically recalculate when their dependent signals change. - Better change detection (using onPush now, but will be built in soon). - Create simple state management features. NgRx greatly expands on this providing more full featured state management. Does that answer your question?

I have access to all of your courses with my current organisation subscription but why this course alone asking for upgrade in pluralsight ?

@deborah_kurata

7 ай бұрын

I don't know. You could try contacting pluralsight support at support@pluralsight.com. I'll ask on my side as well to see if it is a more general problem.

@deborah_kurata

7 ай бұрын

The person at Pluralsight I just spoke to suggested this: "tell him to log in and log out, and try again"

@rishukumar7586

7 ай бұрын

@@deborah_kurata thanks it worked

@erics.a.3875

6 ай бұрын

@@deborah_kurata

is this an AI voice? :)

@deborah_kurata

3 ай бұрын

😥 No, it's my midwestern US tone. You can change the speed of the player in KZread if that helps.

@Storiada

3 ай бұрын

@@deborah_kurata ok, my bad than… sorry for that