All of this has been addressed zillion times. Modern Smalltalk dialects have actor libraries and have code reuse mechanisms that don't involve inheritance. There are ways of doing static analysis on late-bound code. (Obviously, guarantees are not going to be the same. I take that as a reasonable trade-off.) OOP isn't predicated on mutable state and there are ways for the system to manage it anyway. (Although, to be fair - that is one thing from the list that hasn't been fully addressed in any practical OOP system I'm aware of.)
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.
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.