> it falsely assumes OOP is a good approach
I'd say the bigger unspoken assumption there is that Java is good at OOP!
> it falsely assumes OOP is a good approach
I'd say the bigger unspoken assumption there is that Java is good at OOP!
i.e your not really dealing with objects all the time like in smalltalk but just "blueprints" that are a far shadow of what things should be (if i remember the claim correctly)
Alan Kay himself said he regrets coining the term as "object" oriented, and wishes he had emphasized "messages":
Not everything is an object, as someone said, there are also primitives.
There are many other "things" in Java that are not objects (operators, statements, etc.).
Kotlin does set some of this straight. Everything inherits (indirectly) from the Any class. And primitives do not exist in Kotlin (as in Ruby or Smalltalk).