I like it. I think it has the potential to greatly reduce the amount of code one writes. This can only be accomplished if the programmer is well versed in all the technicalities of the OO language in question. The programmer also needs to know what they're wanting to do specifically. You can't just sit down with an OO language and hack together a quick proof of concept as you go. You need a plan before you start since the IDE's used (for Windows and Mac at least) force you into the MVC pattern. The plus side of this is that your code is all nicely segmented and logic is kept with the logic and display code stays where that should be.

I'd also like to point out one thing and a few offshoots from that. Objective-C (Mac) and C# (Windows) are fully object oriented languages. They aim to make programming for users easy which is great but there's nothing worse than a blind programmer. What I'm trying to say is the same as above, even though it's easy a plan is still needed. Also, OO code will always be slower than pure C or C++ but it's the modern world we live in. Most times our computers are using no more than 5% of our CPU resources. It's said that a well designed system uses it's resources effectively, meaning if you program something and it uses resources that's fine. That's what it's supposed to do.

For a final note, from personal experience I'm a believer that if a language wasn't designed for OO from the ground up it should not be used for OO. The prime example that comes to mind is PHP.

Is there any specific part of OO programming you're looking to talk about?