anchor.diff:    developers are working together on one or more projects.</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
     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>
  +  auto-syncing to data models, don't do it. If you do... go for it :-D 
  +  </p>
   
     <p>
     <b>Dynamicism</b> - <s>superfluous</s> has no compilation step. You can
  
positive.code: 
  <p>
  This allows your app to communicate between friendly modules without threading
  a request object through every callback. <a href="https://groups.google.com/forum/#!topic/nodejs-dev/gBpJeQr0fWM">See this google groups thread for more info</a>
  </p>
  </div>
  
  
negative.code: To access each route, the <b>controller</b> and <b>method</b> can be used. For
  example, <code>url_for("my_controller.get_demo")</code> would return
  <b>/demo</b>.  The reverse router can also resolve parameters, so
  <code>url_for("my_controller.get_add", { id: "12"})</code> will generate
  <b>/add/12</b>.
  
  <p>
  The router's build function is available as <b>api.router.build</b> in the
  server controller and <b>url_for</b> inside templates.
  </p>
  
  