[1] https://news.ycombinator.com/item?id=21238802
[2] https://medium.com/@brianwill/object-oriented-programming-a-...
https://tonyg.github.io/squeak-actors/
http://scholarworks.sjsu.edu/cgi/viewcontent.cgi?article=123...
http://scg.unibe.ch/archive/papers/Scha03aTraits.pdf
http://web.media.mit.edu/~lieber/Lieberary/OOP/Delegation/De...
http://bracha.org/pluggableTypesPosition.pdf
http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.134...
Even if none of the work I mentioned above existed, this sort of criticism is amateurish at best. Real engineering requires considering trade-offs in real-life contexts. For example, compile-time checks aren't going to help you figure out that some vendor supplies incorrect data via a web service. An early prototype, however, can do exactly that.
- Modeling all communication as synchronous message-passing. Some communication (such as evaluating mathematical functions) is naturally modeled as synchronous procedure calls, while communication which is naturally modeled as message-passing should be asynchronous by default (to address unpredictable latency, partial failure, etc.).
- Emphasizing implementation inheritance as the primary means of code reuse. This is now generally acknowledged to be a mistake, so I won't elaborate.
- Deferring all method resolution to runtime. This makes the amazing introspective and dynamic capabilities of Smalltalk possible, but it also makes it impossible to statically verify programs for type-correctness.
- Relying on mutable local state rather than explicit, externalized state. This is controversial, and it's a defect of the Actor model as well (yes, passing new parameters into a tail-recursive message receive loop is equivalent to mutating local state). The partisans of OOP and the Actor model believe this to be a virtue, enabling robust emergent collective behavior from small autonomous software agents, but it makes predicting large-scale behavior difficult and debugging nearly impossible.