I think because of "Integration with authentication and authorization". I don't think ui-router does that at all right?
Also Ui-router basically has the
$stateProvider.state(/*.....*/)
From what I understand and have done is use a namespace key for the states. So I think the google angular team is trying to have this whole implementation tied to the set of controllers? Since states lineage and controllers are kind of inherently tied.
1
u/ztbrown Mar 18 '14
Angular should replace its router with ui-router. Why reinvent the wheel?