I've been using the Google Web Toolkit (GWT) for over six years. The GWT team pushes hard on the Model-Viewer-Presenter pattern. Can you explain the relationship you see between object-oriented though (design, programming, etc.) and design patterns such as MVC, MVP, etc.
"Hell hath no limits, nor is circumscrib'd In one self-place; but where we are is hell, And where hell is, there must we ever be" --Christopher Marlowe, Doctor Faustus (v, 121-24)
MVC actually goes back to at least the '80s with respect to Smalltalk. Actually, I was a C and then C++ programmer in the 80's and Smalltalk was my first introduction to true Object-Oriented programming. As you know, back then, many C++ programs were basically C programs that were using a C++ compilers. Smalltalk is a true Object-Oriented language (environment).
MVC was an early and major methodology for modeling systems - GUIs, etc. Just as in Object-Oriented design, the groundwork was put in place for reusing design components that were theoretically robust, tested, etc.
The concept for patterns can actually be traced back to the 18th century architect Christopher Wren. Patterns are all about creating good designs that are robust and reusable.
Trygve Reenskaug introduced MVC into Smalltalk in 1979. I had the distinct pleasure of attending a talk by Trygve last year at SPLASH 2012. It might be of interest to note that Trygve does not consider Java to be a truly object-oriented language, referring to it rather as a "class-oriented" language. I'm still trying to understand that statement but it has something to do with Java's inability to support the DCI (Data, Context, and Interaction) paradigm, another concept that Trygve has worked on for a number of years.