What I'm talking about here is what Alan Kay meant with object-oriented programming (OOP). Grady Booch it's more of an advocate of Java style OOP, which is what we typically mean by OOP today. But that has little to do with what Alan Kay called OOP. For instance Grady works with things like class hierarchies and UML diagrams. That is not part of Alan Kay style OOP at all. Kay is about process isolation, messaging and polymorphism.

The style of object oriented programming that he advocates is something I consider myself done with. I drank the Kool-Aid for years but I'm done with it. However I think that what Alan Kay advocates has merit. Or let me rephrase this slightly: it's not that I don't think Java style of the orient programming doesn't have utility. It is that I don't find it as important anymore. Are used to spend far too much time in the past trying to make my code "proper" object oriented. I don't see a particular value in that anymore. Use whatever paradigm works.

In fact I think you should always attempts first to solve your problem in a functional manner rather than an object oriented manner. If that doesn't work, then perhaps consider an object oriented solution.

When building larger software I think the Allan Kay philosophy is very useful. But I try to steal inspiration from a wide righty of people. I am heavily influenced by the Unix and Plan 9 guys such as Rob Pike and Ken Thompson. I also draw a lot of inspiration from Linus Torvalds, the LISP community, architectural thinking in the game engine community such as data-driven design.