Since you’ve chosen to ignore wide swaths of what I wrote, I’ll only address one response (the rest was largely redundant with what I’d already written regardless).
“BeOS: blather and nonsense. Please don’t post crap like this thinking I’m some code-slave in the next cubicle you can spin your nonsense to. There are lightweight Unix implementations written entirely in C++, there are large parts of the NT code base and supporting apps in C++, and there are large parts of Unix (like CDE) written in C++.”
So, you admit that since BeOS no OS has been written in object-oriented (as opposed to C subset) C++. Specifically as in accessing core OS functionality using C++ objects.
Game, set, match. C++ isn’t suitable for systems programming, nor really for any other large-scale undertaking.
Software development is rapidly moving beyond C++. I hope you’re happy advocating the “new COBOL”. LOL!
I understand you're a failed C++ coder. It's OK. We need garbagemen, too. Thankfully, I don't have to clean out your birdcages; I have more contract time than I can actually satisfy.