Yet to be proven. I never seen a single example of OOP bringing anything but more unnecessary complexity.
I asked for a very simple thing - a piece of code which is easy, robust and maintainable because of its use of OOP. All of the qualities are objective and easy to measure, regardless of your philosophy. There must be at leat some examples of this. If they do not exist, then your claims that OOP eliminates complexity are nothing but religion, not backed by any evidence at all.
How is that a simple thing? What are you looking for? If I showed you a piece of code which was I said was simple, robust, and maintainable, how would you know whether it's true or not, unless you know the language, the problem it's intended to solve, and have a personal history of maintaining it?
No, you're asking a question with no possible answer, and then intended to use that lack as proof in your own mind.
Why people are so keen on solving problems they just created for no good reason at all?
Can you find anyone who agrees on what "correctly executed OOP" is? I don't think there is a consensus on this idea, nor any particularly objective criteria for how to achieve good OOP.
I do not buy that.
The reality is, that when OOP is correctly executed (and there is the real culprit, since few people have really understand it!) it really can help you to lower the complexity of programs -- and that is decisive, not some halve-religious statements.
[1] One example: Inheritance vs. Composition -- even OOP people have seen the problem that overuse of inheritance is bad. But they don't throw the whole thing out of the window, but tell where to use it or restrict its usage. Don't just find the problems and fanatically throw all (even the good stuff) out of the window!