To be honest, the real pattern is MVW (Model View Whatever).

The third thing can be a controller (true MVC), a presenter, a view-model, or, in the case of the article, operations and events.

The big deal with all this is that we have a view, usually provided by a UI framework, a model, usually provided by the app developer, and some kind of loose coupling. That's it, the good old idea of separating data from its representation.

What you stick between the model and the view is just an implementation detail of your particular framework, optimized for your particular use case.