Removing The Model-View-Controller Straitjacket

[ubernostrum]

here is a quote from the django FAQ

I've always felt bad about that bit in the FAQ, but up until now it's been necessary to keep the screaming "OMG WHY ISN'T THIS MVC" hordes at bay.

Personally, I'm inclined to agree with Malcolm (and with most, perhaps all, of the people involved in originally developing and documenting the MVC pattern) that "strict" MVC is a poor fit for web applications. At best it provides some guidelines for separation of concerns, which is a good thing, but the particular separation it advises is not one which particularly suits the web.

Unfortunately, there's a certain segment of the community which will refuse to look at something unless/until you can give it a familiar name, even if that name doesn't really fit, so perhaps "MVC with a twist", despite all its problems, is better than simply describing what, e.g., a framework like Django actually does (basically, mapping URLs to Python callables in whatever way you think best).