title: How do Meteor's blaze and Famo.us play together?
body: <p>2 Technologies:</p>
  
  <ul>
  <li>Meteor with the blaze templating engine</li>
  <li>Famo.us with their awesome gui framework</li>
  </ul>
  
  <p>I come from the meteor side, I personally like using {{mustache}} (handlebars) to drive the gui from data, the reactive session / database makes this really efficient and intuitive.</p>
  
  <p>Now came famo.us and all its advantages, but the drawback of a code based gui is that there is no place for handlebars anymore…</p>
  
  <ul>
  <li>What is the current practice for mixing both technologies together ?</li>
  <li>Are they completely dissociative ?</li>
  <li>Is using the "observe" / "Deps.autorun" mechanism a common practice everywhere a famo.us element to be updated by a meteor reactive item ?</li>
  </ul>