From what you are saying I guess you have never been in an OO project but you just worked in the "cold hell" of procedOOral code, the worst mix of copy and past

From what you are saying I guess you have never been in an OO project but you just worked in the "cold hell" of procedOOral code, the worst mix of copy and paste, overblown inheritance and singletons. I experienced a lot of it in my career, nowadays I am more oriented towards the functional world, but saying that OO is completely useless and even dangerous is an outright lie. The most awful codebases on which I worked on would have been quite nice applying the OO best practices. Sadly they where far too big to be changed by the concerted effort of a couple of people. And they were full of anti-patterns. Even loving the type safety of F# and Haskell I can't honestly say that OO is an anti-pattern per se. What it matters is not the size of the hammer but how you use it. But I can rightfully proclaim that the wrong tools used for something that they were never meant for are the worst possible solution. EVER.