title: Game framework architecture - view components or MVC?
body: <p>I'm trying to build a very light re-usable framework for my games, rather than starting from scratch each time I start a game. I have a component driven architecture - e.g. Entity composes a Position component and a Health component and Ai component etc. </p>
  
  <p>My big question is whether my <strong>model composes view components</strong> to allow for more than one view of the model, or whether to use a truer MVC where the model does not know about its views, and they are managed externally.</p>
  
  <p>I have tried both methods but if anyone knows the pros and cons of each approach and which is the industry standard, it would be great to know.</p>