> But beyond that, regardless of what the "MVC" is, we've still got some sort of separation going on. But the separation is often pointless. Django divides thi

> But beyond that, regardless of what the "MVC" is, we've still got some sort of separation going on. But the separation is often pointless. Django divides things into models, views and templates, which correspond to most other web frameworks' models, controllers and views. One reason this division makes perfect sense is that the views and templates are worked on by different people. The templates are mostly HTML with some markup language and will be the responsibility of the designers. The views and models provide functionality and will be worked on by more backend-oriented programmers. Another reason is that the views are actually reusable. You have generic views for browsing a model by date, or for a simple edit form. You can bind them to a model and skin them with a template to quickly get basic functionality that would otherwise require boilerplate.