3 ms·

> When writing iOS applications I also usually end up with something that is better described as M-VC than MVC, where the view and the controller are tightly co

> When writing iOS applications I also usually end up with something that is better described as M-VC than MVC, where the view and the controller are tightly coupled and basically the same class. This is not how the MVC pattern was intended. No, but if M-VC works, then it's fine. MS used Document/View architecture where the View was decoupled from the Document (model) in MFC and that was very popular and successful for years. "The humble dialog", IIRC, describes something similar. I don't think we developers should fear the wrath of the the MVC police if we choose not to decouple everything.

stcredzero 10y ago
A lot of the codifying of MVC happened in Smalltalk. However, the reality of Smalltalk development is that most people had Model objects, then stuck everything into instance slots of an instance of an "ApplicationModel" subclass. Originally, ApplicationModel was called "GluePuppy" because it was just an arbitrary thing on which to stick other things. So who in the world are these MVC police? Does anyone in the world actually do MVC correctly? Has anyone ever?