Does OOP serve a purpose?

Aside from encapsulating data well and making generalisation fanbois wet?

I'm not sure what problem OOP set out to solve, but on its way it created so much more problems I now have to deal with frameworks that probably have more than a thousand classes and interfaces in it. Most of which don't really seem to do much of anything and have names such as "AbstractService", "DependencyInjectionConsumer", "ContentFactoryController" and "ContentFactoryControllerFactory", etc... OOP seems to try to solve every design challenge by adding more classes / design patterns to make the code more customizable and complex.

In the end, it often gets hard to see the forest for the trees and this slows down development. (Think UML.) I think the bulk of most programs can be written in a procedural style, which is generally cleaner and easier to follow.