Bad things about C++

Since the python thread was a smashing success, it's only logical to have a C++ equivalent. So list the bad things about C++. Constructive thread, please. I will get the ball rolling:

 * Segment faults.
 * Broken standard library.
 * One word, the forced indentation of code. Thread over.
 * Broken templates.

>>26
The fact that you think that having no garbage collector is "fast and control" indicates that you're just as much a nub. Unless you're allocating everything on stack or writing your own memory handlers and overriding new, it's not deterministic either. When was the last time you looked at the most common heap allocation algorithms?

Anybody who is worth their salt will preallocate before entering a performance-critical section, no matter whether the language uses manual memory handling, automatic, or both.