title: Major design differences between Angular, React, and Blaze (client-side Meteor)?
body: <p>I've seen the Angular vs. React, vs Meteor questions asked a number of times. On the meteor side inevitably the answer to that question is an explanation of how meteor is much larger in scope (has DDP, deployment, all the server side stuff, and all the other things it provides).</p>
  
  <p>I want to restrict this question to only the Blaze engine and things where they do somewhat overlap, especially where either one may provide additional features and/or capability in terms of writing or structuring the client side code.</p>
  
  <ul>
  <li>Where are they complementary to each other? (e.g. what does <a href="https://github.com/lvbreda/Meteor_angularjs" rel="noreferrer">https://github.com/lvbreda/Meteor_angularjs</a> bring to the table)</li>
  <li>Assuming the above brings certain advantages, how do you compensate for that if using pure meteor? </li>
  <li>Given that angular encourages a fairly strict separation of code on the client for MVC, how should one structure good code on the client in meteor to follow its MVVM pattern? (Does it just come inherently from having template, client module(s), and a model)</li>
  </ul>