After a lot of intense inner debate and deep concentration, Ive finally come up with a phrase that summarizes my feelings on the subject:

Objects are just meatballs in spaghetti code!

OOP is founded on important principles, modularity, code organization, but the tradgedy is that instead of talking about applying those principles, the conversation is sidetracked into "objects".

The reason this is troublesome is that instead of objects being one tool in the toolbox is it viewed as an autopilot to always produce supperior code. And this blindness leads to less clear code.

There are other more factual problems such as by making a program understandable in small pieces, the program becomes less understandable as a whole. Or that carrying state around in a multitude of places is a bad idea for maintainability. But Ill leave the factual arguments to others who are more diplomatic than I am.