Hi Derek, This is the main reason a lot of us warn against too many watches. For me personally this is more important then the often mentioned performance issues. For lots of situations you do not need a watcher, avoiding them is the best measure you can take to prevent over-usage. If you go the other way, and do everything with plain events (what the $broadcast/$emit/$scope.$on) is you end up with actually the same mess. To me this feels even more brittle, as you never know who is listening where to what events. (wow that's pretty vague). You have put some though into in, as I see you have even come up with using _throttle. I would advise you not to go figure this out yourself, but instead look for existing solutions. Enter the world of Reactive extensions <http://reactive-extensions.github.io/RxJS/>. (there are alternatives for this. but I found this the most complete/mature version, there is even an angular extension <https://github.com/Reactive-Extensions/rx.angular.js>) I think this will perfectly team up with angular, and addresses exactly the issue you are having.
Regards Sander -- You received this message because you are subscribed to the Google Groups "AngularJS" 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 http://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
