you don't know what the fuck OO is in the first place
Nobody agrees on the definition or formal characteristics.
And nobody agrees on who gets to decide the definition. There is no standards body who defines what OO is. YOU are not it.
Every tool has a proper place and use, and making relative value judgements between them is something fuckwits do when they only know how to use one thing.
I've mentioned multiple times I do choose to use it to some degree. I've found practical utility for it under certain circumstances. So what is this "one thing"?
how you've rooted out this terrible OO hoax perpetrated on the industry
Well, okay, "hoax" is possibly a little harsh, but I do believe that OO-domain-modeling was thrust on the industry by hucksters wanting to sell books and consulting services; and millions, if not billions were spent chasing this false dream.
The primary focus of these hucksters was in domain modeling. Therefore, other than a small blurb, I didn't used to make much of a distinction between "OO" and "OO domain modelling".
A bigger distinction is made now in the industry because practical experience and failures taught many that domain modeling is NOT where OO shines. I know you disagree that domain modeling was the main stated selling point of OO, but we'll just have to let that disagreement stand (unless somebody can present reliable surveys of beliefs).
Why does it matter to you anyhow? It's water under the bridge. I'm not understanding your complaint. It appears you want to make this all about me instead of OO. That's why you appear to be a troll. Non-trolls talk about the subject at hand. Say something about OO and than back your claim with evidence: that's not asking too much.
You seem to agree there that scientifically comparing the utility of software engineering paradigms/techniques is either a gray art or requires resources not yet committed by anybody. Good, that part is mostly settled then.