> Ember's routing is just flat out better than anything else I've seen out there.
I'm the lead developer of ui-router. I've read everything I can about Ember's router, and I just don't get it. Barring some boilerplate-saving conventions (we don't offer any, but we do offer APIs that let you roll your own pretty easily), could someone explain to me what the big deal is?
Also, re: the score-keeping thread, I know Angular is used extensively within the BBC.
I just recently started using Angular, but ui-router definitely gave me a bit of trouble. I had to dig through StackOverflow to find answers to questions like how to enforce that certain views must only be accessed when the user is logged in. Another bit of trouble I had was doing things like logging the user out, then immediately redirecting them to the login page. Had to redirect then to the home page so that the state change hijacking code fired and redirected a second time.
I can definitely see that ui-router is a valuable component and it's very powerful, but perhaps I have not achieved the zen of it yet.
I didn't get that part either.
ui-router works well for me and doesn't have equivalent issues to rendering nested routes in the same outlet I had in Ember.
> Ember's routing is just flat out better than anything else I've seen out there.
I'm the lead developer of ui-router. I've read everything I can about Ember's router, and I just don't get it. Barring some boilerplate-saving conventions (we don't offer any, but we do offer APIs that let you roll your own pretty easily), could someone explain to me what the big deal is?
Also, re: the score-keeping thread, I know Angular is used extensively within the BBC.