anchor.diff:  controller</b>. The server controller is the entry point for the app. It
   renders the app by placing <b>components</b> into <b>templates</b> and
   <b>partials</b> and delivers the constructed app to the browser, where the
  -client controller is initialized.
  +client controller is initialized and handles further user interactions.
   </p>
   
   <div class="mtl mbl">
  
positive.code:   jQuery selectors - it's up to you. if  you don't like the idea of templates
    auto-syncing to data models, don't do it. If you do... go for it :-D </p>
    <p>
    <b>Server - Client Cohesion</b> - sometimes, coupling is a good thing. Using
    two controllers allows the app to organize itself in a way that makes sense
    for the server and the client, allowing components to exist in many contexts.
  
negative.code:   download assets while the slower parts of the page are still generating.
    </p>
    <p>
  
    <b>Flexibility</b> - <s>superfluous</s> handles many boilerplate tasks but
    still leaves the developer freedom to architect their web app - whether it's
    choosing how to render, which data layer to use or how to split the client and server
    responsibilities.
    </p>
  
    <p>
    <b>Re-usability</b> - Components encapsulate re-usable portions of rendering,
    event handling and data synchronization code. Using components on a site adds
    structure, well defined behaviors and division of responsibilities.
    <br />
    Components can be rendered on the server or client and treated as the same
    instance. This eliminates much of the tedium of creating rich and re-usable
    interactions.
  