title: What should own the model in an MVC pattern?
body: <p>I have been making iOS apps since I can remember, but I haven't matured my programming style much until recently when I got an internship programming. I learned many OO concepts early on because I realized that life sucked with out an understanding of them, but one thing that I never made myself learn was the MVC pattern.</p>
  
  <p>To give context, let's say that I'm drawing a solar system inside of a single <code>SolarSystemView</code> (a subclass of <code>UIView</code>). Should my <code>SolarSystemView</code> have an instance variable of class <code>SolarSystem</code> (a class containing a data structure with all of the important planetary and stelar properties), or should that be under ownership of an instance of a <code>SolarSystemViewController</code>? Or is it something completely different? I can't find any example  code that gives a satisfactory answer.</p>
  
  <p>I imagine that if the view owned the model, operations would be very smooth, but that also doesn't feel like good style. After all, the <code>SolarSystem</code> instance has to change dynamically somehow, and with the same or similar rate that the <code>SolarSystemView</code> updates.</p>