`  It means that if you're familiar with MVC you'll recognize the architecture, though some things don't go by exactly the same names; the same separation of concerns  data modelling, routing, database interaction and presentation  are all kept in well-separated components just as in a stricter MVC design, but the naming is different. Django's templates, for example, embody the pure presentational logic which is called the ``view`` in strict MVC, and a Django ``view`` actually does most of the duties of a strict-MVC controller (database interaction and selecting a template to use for presentation). These differences arise because, historically speaking, Django is more concerned with ease of use and practicality than with design-pattern purity.  `