anchor.diff:    <div id="routes_example" class="collapse no-transition">
     <pre class="prettyprint"><code>{
       "/": "about",
  -      "/demo": "demo",
  -      "/kitten": "kitten"
  -  }</code></pre>
  +    "/demo": "demo",
  +    "/kitten": "kitten"
  +}</code></pre>
   </div>
   </div>
   
  
positive.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 much work should be
    done on the server or client.
    </p>
    <p>
    <b>Reusability</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.
    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.
  
negative.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.
  