In a response to John Lim's posting about MVC being over-designed crap, Jeff Moore has a new post over on his blog with a rebuttal.

John Lim has a recent rant asking Is MVC over-designed crap? I used to think so, but now having refactored some existing applications to use MVC, I see the value.

[...] Is there confusion over MVC? Yes. Many of the "what goes where" arguments are a bit like trying to count the number of angels that can dance on the head of a pin. In practice, a 100% separations M, V, and C concerns is almost impossible and not even desirable. Yet, it turns out that making some kind of distinction between the concerns is helpful.

He continues on talking about what MVC really is all about and how much the "broader your definition of MVC, the more trouble you are going to have with the "what goes where" and "where does this go" questions". He gives an example of a GUI applications written in Visual Basic or Delphi to show how using a controller in your application can be leaps and bounds above other, more random methods of application development...