This article does not describe a "true" MVC, but a popular modification based on frameworks. However, it is not a "true" MVC and has quite different properties.
The view (presentation) is responsible to display the data provided by the model in a specific format. It has a similar usage with the template modules present in some popular web applications, like wordpress, joomla, …
View is not created by templates only, but also by the presentation logic (pagination management, etc.)
The controller handles the model and view layers to work together. The controller receives a request from the client, invoke the model to perform the requested operations and send the data to the View. The view format the data to be presented to the user, in a web application as an html output.
This is the primary misunderstanding of MVC. If anyone takes a look at the original definition of this pattern, he can see that the controller does not serve as a proxy between model and view. It only selects them and communicates one with another, then the view retrieves all the necessary data from models directly, using well-defined, generic interfaces. It may seem silly, but this simple issue changes the properties dramatically. The original MVC leads to the development of bettwen interfaces, reduces the dependencies between the three layers and makes the entire application more flexible. In so-called "web framework MVC", most of the code, often including the business and presentation-specific logic, is moved to controllers, and most of the "flexibility" and speed is achieved thanks to code generators, not the design pattern itself. Actually, many web frameworks make things even worse, reducing models to ORM, which makes almost impossible to use other-than-database data sources in a convenient way, and breaks one of the MVC rules.
PS. I have only one point: if anyone finds the "modified pseudo-MVC" convenient, that's all right. But he shouldn't write it is MVC. Design patterns were "invented" to define an unambiguous terminology for useful design techniques, so that anyone who sees i.e. "pattern XYZ", could understand it precisely. For me, calling an MVC modification simply "MVC" is like throwing away observation from Observer pattern and claiming it is still Observer.