Hands-On Design Patterns with Swift

The theory behind the MVC pattern

Let's go back to the original description of the design pattern:

• Model classes are used to represent knowledge and data. A model can be represented as a single object or structures.
• View classes are used to represent the data to the user.
• Controller classes are used to validate input from the user, passing it to the model layer.

Now, there's a word that isn't properly defined: user. Usually, when we program applications and algorithms, the user is the human being at the other end of the program. This definition is misleading, as it perpetuates the idea that there should always be a human being inputting information into the controller, and that views are always graphical interfaces.

I would like to challenge ...