Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

3
  • 5
    This is key. MVC works really well in web applications, and indeed is a large part of the reason why modern MVC-based frameworks (like Rails, Django, and ASP.NET MVC) are so popular. It works in other contexts (like desktop apps) too, but it is harder to keep a clean seperation of view and controller, so variants that remove the view-controller seperation like Model-delegator (used by Swing) or change where the split occurs like Model-View-ViewModel (used mostly by .Net WPF apps) are more common in Desktop Applications. Commented Mar 21, 2012 at 15:46
  • If you look at the original Smalltalk description of what a controller does -- translate user input into messages for the model -- Windows itself is basically one big controller; that's why MVC as a pattern doesn't mesh very well with Windows UI applications. Its used a lot more in UI Frameworks for non-Windows systems. Commented Mar 25, 2012 at 3:38
  • @MichaelEdenfield Not really; you can do MVC and WinForms together, although MVP is more popular there, but MVP is a variant of MVC anyway. Commented Nov 8, 2014 at 17:49