I regard the MVC pattern much like the OSI 7-layer network model: it’s a way to think about the problem space. That doesn't mean your implementation will necessarily implement every single layer of the pattern or the model: it explicitly defines the conceptual model and your implementation can choose to optimize as needed. In that light, Apple's MV pattern is an optimized variant of MVC where some of the responsibilities typically assigned to the controller are absorbed elsewhere.