The "missing the point" argument is a little bit easy. It's not that I don't understand OOP - I do, and I've done far too much of it. I understand it, and I r

The "missing the point" argument is a little bit easy. It's not that I don't understand OOP - I do, and I've done far too much of it. I understand it, and I reject it as a useful paradigm for any of the classes of program that I would like to write. That's an easy "out", right? Whereby it's easy to say "oh, you obviously don't write programs of type x", but I have enough confidence in my experience doing both general-purpose commercial programming and very specialist research programming to think that I can at least make that judgement on the basis of a reasonably large set of problem domains. Perhaps there are domains that match OOP really well. I just haven't found them yet. And I'm not sure where you are getting most of these criticisms. Did you actually read to the end?