title: specifying AngularJS controller: benefits using ngController vs. $routeProvider
body: <p>There are two ways (AFAIK) to associate a controller with a view template/partial: the route specified in <code>$routeProvider</code> and the <code>ngController</code> directive. Especially (but not exclusively) for simple routing, is there any benefit/efficiency of one over the other?</p>
  
  <p>My project currently uses the $routeProvider approach, but I've been given the task of nesting views. This seems simple enough with ngInclude, as long as the partial specifies its ngController.</p>