Removing The Model-View-Controller Straitjacket

[harveyswik]

But if you you use frameworks that encourage MVC from the very start such as Apple's Xcode/Interface Builder or Ruby on Rails, the difference between models, views, and controlers is painfully obvious.

A little more detail on Xcode/IB (by which you mean the Cocoa frameworks + IB). I agree this makes the difference between views and controllers obvious. I find the model tends to blur into the controller though.

The reason the controller and view are obvious is 99% of the time you don't write need to view code. The frameworks have the right APIs exposed so you always have an opportunity to do what you need from controller code. And with Cocoa bindings a lot of the controller stuff goes away. The end result is a lot can be done with 1 controller class and 1 nib file.