|
|
|
|
|
by archevel
2918 days ago
|
|
> Have we really not understood OO at all so that we have to reinvent it all the time? We haven't. I think the popular OO languages shows this. In both Java and .Net the focus is on classes, not on messages passed between objects. But class hierarchies are not essential for message passing. Classes are mainly a way of decomposing an application into manageable logical parts of interacting chunks. Looking at how many language features center around classes and class hierarchies (interfaces, abstract classes, generics, inheritance etc) as opposed to how many facilitates different forms of interactions between objects (you basically have method calls and arguably async/await) it seems clear to me that these languages are more "class oriented" than object oriented... |
|
React UI? Smalltalk already had Observer and event messages.
java.util.Observable exists since version 1.0.
Interfaces are lousily based on Objective-C categories, and the first edition of "Component Software: Beyond Object-Oriented Programming" using Component Pascal, COM, Java was published in 1997.
The second edition added C# examples.
Which are concepts that now everyone is discussing as Entity–Component System.
Our field would be much better if there was less pop culture and more book/paper reading.
EDIT: forgot to add the publishing date