OOP to me means only messaging, local retention and protection and hiding of state-process, and extreme late-binding of all things. It can be done in Smalltalk and in LISP. There are possibly other systems in which this is possible, but I'm not aware of them.
About this quote
- What does it mean?
- True object-oriented programming focuses on messaging, encapsulation, and late-binding rather than just class structures.
- In plain terms
- True OOP is about messaging and hiding state, not just classes.
- What can you take from it?
- Focus on messaging and encapsulation in OOP.
Where it applies
Putting it to work
Questions to consider
- What defines true object orientation?
- How do you hide state effectively?
Another view
Many languages claim OOP without supporting late-binding or encapsulation.
More from Alan Kay
Most software today is very much like an Egyptian pyramid with millions of bricks piled on top of each other, with no structural integrity, but just done by br…
Permalink to quote #6 Perl is another example of filling a tiny, short-term need, and then being a real problem in the longer term. Basically, a lot of the problems that computing h…
Permalink to quote #8 Technology is anything that wasn't around when you were born.
Permalink to quote #5
Related quotes
There are probably better ways to do that, but it would make the parser more complex. I do, occasionally, struggle feebly against complexity... :-)
Larry WallLarry Wall quote #23 The choice of approaches could be made the responsibility of the programmer.
Larry WallLarry Wall quote #116 First were the thick stone walls, the arches, then the domes and vaults - of the architect, searching out for wider spaces. Now it is concrete-reinforced that …
Oscar NiemeyerOscar Niemeyer quote #1