Hi Rahul,

There are even more variants available. The answer depends on your team. 
What do they already know? what is their background? If they are really 
comfortable with observables(rxjs) you might even roll your own state 
management. Heck, you can do that without observables even. 

What all of those have in common is 1 single thing. They make handling 
state way more explicit and provide a set of helpers for that. Also they 
all kind of imply that "everything immutable" is the sole answer to all of 
this. I know it helps, but there is a cost, that often is swept under the 
carpet. Also, most of those trade developer UX in for memory and 
CPU cycles. Those are cheaper those day's but still not free! 

Regards
Sander

-- 
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/angular.
For more options, visit https://groups.google.com/d/optout.

Reply via email to