anchor.diff:  <h3>MVC</h3>
   
   <p>
  -if you are familiar with django, rails or other frameworks, you'll recognize
  -them as MVC. (Models, Views &amp; Controllers).
  +if you are familiar with other frameworks, you'll recognize them as MVC.
  +(Models, Views &amp; Controllers).
   </p>
   
   <p>
  
positive.code: <h2>Features</h2>
  
  <p>
  <b>Speed</b> - <s>superfluous</s> has the initial delivery speed of a server app,
    and the rich interactions of a client heavy app. By delivering the main core
    of the page to the client ASAP, the client can display the app and
    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.
  
    <div class="alert">Many large web codebases today are using Component based
    page generation on the server to minimize development friction.</div>
    </p>
  
    <p>
    <b>Familiarity</b> - Components are simple backbone views with a known
    lifecycle: initialize, render, destroy.  How the component updates its DOM
    tree is up to the developer. It could be MVVM and a data binding engine or
  
negative.code:   auto-syncing to data models, don't do it. If you do... go for it :-D </p>
    <p>
  
    <p>
    <b>Dynamicism</b> - <s>superfluous</s> has no compilation step. You can
    require() your modules on the client or server and load a page. The server
    takes care of dependency graphs, minification and all that packaging stuff
    for you.
    </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.
  