Re:Angular 2.0
by fiatjaf on Tuesday March 18, 2014 @10:49AM
(#7422228)
I have been successful by instantiating separate services to perform REST operations and a global event emitter to establish communication between all the services and all the components that relate to these services in any way.
[ Parent
| on HN ]
Re:Angular 2.0
by marknutter on Tuesday March 18, 2014 @11:01AM
(#7422321)
I cringe when I hear the words "global" and "event" together in the same sentence. Projects I've worked on in the past that relied heavily on global events often became a maintainability nightmare.
Why? Please share your experiences. I don't understand what's the utility of event emitters if not for serving as glue to all the separate components of an app. Am I wrong?
Re:Angular 2.0
by marknutter on Tuesday March 18, 2014 @02:06PM
(#7423770)
You're not wrong. It's definitely one way to solve it. I just find it harder to jump into a project with heavy reliance on global events and be able to quickly understand what's going on. It gets even harder if you have events firing other events.
> I just find it harder to jump into a project with heavy reliance on global events
Harder than what?
Re:Angular 2.0
by marknutter on Tuesday March 18, 2014 @10:53PM
(#7426551)
Harder than the way that it is done in Angular, via services.