> When exploring how a web app should work, you should be thinking at all levels: view, controller, model. And separating those aspects programmatically makes

> When exploring how a web app should work, you should be thinking at all levels: view, controller, model. And separating those aspects programmatically makes it easier to think about them, not to mention program the ideas that occur to you when thinking about them separately. > If those generic tools are the best ones for the data model being manipulated, why involve a programmer at all? If intertwining essentially unrelated ideas is the best way to write programs, why use high level languages at all? MVC--just like garbage collection, just data abstraction, just like most other high level languages features--is about modularity and separation of concerns. > We would have much more interesting and varied web applications out there if the prevailing "wisdom" of MVC would die. How do you reconcile this with the fact that there occurred a veritable explosion of various interesting web applications when MVC was (re)discovered by the webdev crowd?