MVC Isn’t MVC
> Model updates View, View sees User, User uses Controller, Controller manipulates Model.<p>> This makes a lot of sense to me, and I think I understand it pretty well.<p>It looks simple at first glance, but it actually makes zero sense under closer inspection.<p>Let’s take a simple example. A table of users. You take a table from the database and put it into an html tag table. Wait, who is “you”? The model? Do you want your model to know about html? The view? Do you want your view to know how to connect to a db? The glue code for them? If so, then it is  the model-view-controller-glue, not model-view-controller.<p>This is why what the author calls Apple-MVC is far more common. It is just hexagonal architecture. You take different components that take care of their own area of concern and glue them together to fit specific needs of your app. That glue code is called “controller” in that case. It is intuitive and simple; and thousands of junior developers probably reinvent that type of architecture every day.