That said,
> Even if Java had multiple inheritance, it should have had also the interfaces to be able to become the usable language it is today.
I have a problem with this assertion. I don't think Java-like interfaces are required for an OOP language to be usable. What about other OOP languages that don't have them, like for example Scala?
interface Function { call(...); }. // of course this is a made up syntax.
For most of the cases, this is just enough (as it is also in Java).
In any case, my point is that since there are usable OOP languages without Java-like interfaces, this kind of interfaces isn't necessary. That is, there are alternative ways of producing usable OOP languages. It doesn't necessarily follow that Java is successful because of its implementation of interfaces.
Note I think Uncle Bob's condescending tone in TFA is pretty useless. The entire article consists of building a strawman. He really annoys me.
Again, Objects aren't Java interfaces, so I guess the whole discussion is moot :)
There are of course other abstractions with their own benefits.
Uncle Bob wasn't arguing against the general concept of an interface, but about its specific meaning in Java.
Even if, as author thinks, that idea of the interface was invented by accidence, it is a good invention.
Because it allows us to clearly to separate the abstract concept from its implementation(s).
Even if Java had multiple inheritance, it should have had also the interfaces to be able to become the usable language it is today.
While interface would allow us to simulate the multiple inheritance, its main benefit is clearly wider.