title: Separation of Concerns in MVVM
body: <p>I am working on understanding MVVM better, and from trusty Wikipedia (and lots of other research), I have gathered that the ViewModel holds presentation logic and the Model holds the business logic.</p>
  <p><a href="https://i.stack.imgur.com/sSnki.png" rel="nofollow noreferrer">MVVM Pattern (Image courtersy of Wikipedia)</a></p>
  <p>My question is, how is there a separation of concerns between logic and data when the Model is holding the business logic? Why is this a good pattern and why would I want to use it instead of using MVC where the Controller handles business and presentation logic (if I understand it correctly)? (I am using WPF, which based on my research, mainly uses MVVM and rarely uses MVC, and I still don't understand why).</p>