Greetings, Reading this post, and your other one regarding observables makes wonder the point you wish to make.
Certainly most angular 2+ applications do not need redux, nor a 'store' of any kind. This AiA podcast with Wes Grimes makes that rather clear https://devchat.tv/adv-in-angular/aia-260-ngrx-the-mystical-machine-with-wes-grimes/ Keeping in mind that your sample code is very simple, I wonder how you expect your component to show "Name: Susan" when some other component has changed the value in the store after the setTimeout has fired. I believe Observables would be the easiest mechanism for that. Additionally, if you're writing code that other experienced angular developers will need to maintain, I expect they'll be surprised finding lots of setTimeout calls sprinkled around rather than using Observables. Perhaps you used setTimeout simply as an alternative example of updating values w/o using observables. Event listeners would also be another example. -- You received this message because you are subscribed to the Google Groups "Angular and AngularJS discussion" group. To unsubscribe from this group and stop receiving emails from it, send an email to angular+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/angular/622c4020-edfa-4834-916c-4e418fe68c90%40googlegroups.com.
