I think you are a step further down in the a/b problem tree.
The purpose of society is that everyone can have a safe, stable and good life. In our current setup this requires that most people are employed. But that's not a given.
Think of a hypothetical society where AI/robots do all the work. There would be no need to employ everyone to do work to support unemployed people.
We are slowly getting to that direction, but the problem here is that our capitalist society isn't fit for that setup. In our capitalist setup, removing the need for work means making people unemployed, who then "need to be supported" while the rich who own/employ robots/AI benefit without putting in any work at all.
I could maybe have been clearer when saying "significant capacity".
Most projects I worked in did use OOP in some capacity, but only in quite small amounts.
My point mainly was that a lot of people think that using the keyword "class" for structs (aka data classes) or modules (aka service/controller classes) counts as OOP and that's not the case.
But I agree that Java and similar languages could use some other type of syntactic sugar for modules. But then again, it would literally just be another name for the same thing.