@gattra wrote:
It seems like with most MVC's, the router routes to a controller which grabs the model and passes it to a view, then returns the view to the browser.
But Ember is now shifting away from controllers and instead having us rely on routes for a lot of (if not all) the logic that the controller would typically handle.
Why not instead just get rid of routes and have controllers behave like a normal controller would? It always seemed odd to me that the route was responsible for grabbing the model instead of the controller anyway.
Posts: 3
Participants: 3