"? Just because an application responds to events does not mean it is "event driven". Event driven means it spends much of its time waiting for an event and then takes action if and when an event occurs . Contrast this with some programs that do not respond to events at all, but simply do their job and terminate. For example, an operating system command to display the current time. It displays the time and is done; it does not wait for events. For more information, see: Event-driven_programming Implementations The pattern was first described in 1979 by Trygve Reenskaug, then working on Smalltalk at Xerox research labs. This original implementation inspired many other GUI frameworks such as: The NeXTSTEP and OPENSTEP development environments encourage the use of MVC. Cute Fashion Model Cocoa, based on these technologies, also uses MVC. Microsoft Foundation Classes (MFC). "

" The controller does not pass domain objects (the model) to the view although it might issue a command telling the view to update itself. The user interface waits for further user interactions, which begins the cycle anew. Benefits and liabilities Although widely used, MVC has both advantages and disadvantages compared to other design options, and individual circumstances should be used to choose the most appropriate design. We discuss some of those here. View instability vs. model stability If constructed correctly, models can enjoy a fair degree of stability (owing to the stability of the domain model), whereas user interface code usually undergoes frequent and sometimes dramatic change (typically because of usability problems, the need to support growing classes of users, or simply the need to keep the application looking "fresh"). Separating the view from the model makes the model more robust, because the developer is less likely to "break" the model while reworking the view. Teenage Fashion Model Attempting to stitch these two worlds together in a hand coded method without architecture is very common, and results in the model object being polluted with knowledge of the interface, and vice-versa. This makes the code very inflexible and difficult to maintain. "