" The unfortunate side effect of this is that the domain of the problem often isn't clearly understood by the programmers until late in the implementation process. Thus, just at the time that the developers are finally competent to create a good interface, they are kept from changing it . MVC models allow the code to be more flexible later in the development process, allowing for changes that make sense at the time it makes sense to make them. Event driven In contrast, objects in object oriented programming are composed of methods and data members that attempt to model something from the domain of interest. The best models are fully encapsulated, meaning that they implement every aspect of that real world object of interest to the domain of interest, and that they don't have any extra code that doesn't model the real world. Encapsulation also means that the class is implemented in such a way that the internal representation of data is not exposed to the user of the object. The impedance mismatch between these two worlds, that of events, and that of objects, is something that's been recognized for a long time. Modular Model Railroad Layout Getting these two worlds to cooperate requires a lot of 'glue code' to make them work together. The 'model-view-controller' paradigm introduces the controller object in between the view (the GUI class) and the model (the object) to communicate between the other two objects. "

" There is one very careful study by a Dutch graduate student, applying the methods Ed Herman used in studying US media reaction to elections (El Salvador, Nicaragua) to 14 major European newspapers. [. . . ] Interesting results. Discussed a bit (along with some others) in a footnote in chapter 5 of my book "Deterring Democracy[". ] [3] References Chomsky, Noam. Life Like Model Railroad Understanding Power: the Indispensable Chomsky. New York: the New Press, 2002. "