I've spent over a decade writing C++ code professionally for financial, insurance and CRM systems. So Stroustrup made a half-baked badly designed partially-OO langauge that has set back the evolution of real OO back at least two decades, and he gets an award? A kick in the ass would be more appropriate.
I have lost count of the number of times I have ran across a mess of C++ code where someone was trying to implement Smalltalk-style semantics in C++. Which doesn't work.
C++ rewards good design but brutally punishes poor designs. And most C++ coders aren't very good at designing clean class hierarchies. This means that most large C++ programs end up being insane vats of code goo after a few years.
Oh, and pet peeves...
The class mechanism in C++ is used to implement several incompatible concepts that would be best separated. One of these is "objects". Objects ideally are almost always used in pointer or reference context, use inheritance, and all public member functions and their destructor should be virtual (a class with a virtual function and a non-virtual destructor is a memory leak waiting to happen). Objects should almost never use operator overloading. Another concept is "values". Values use the copy-constructor and assignment operators, should almost never use inheritance (because getting a virtual assignment operator to work sanely is hard, and a virtual copy constructor isn't really possible) and might use operator overloading. Any case where these two concepts mix is very rarely good.
On the other hand, I can bill $1000/day telling people in painful detail that they have a screwed up mess of code. So C++ is at least rather lucrative for me.