C++ and copying

Why the fuck does everything in C++ insist on endlessly copying shit here and there, spawning 4 (FOUR!!!) copies of some fucking object during certain calls to methods of stdlib containers (vector, tuple etc).

I can't create a fucking thread without it copying my ``functor'' object (with operator()) at least twice for some fucking reason.

So yeah, if you want fast C++ programs, you fucking write them in C, with manual handling of pointers and shit.  Fuck C++.

>>31
copies everything by default
Because C/C++ has no garbage collector, so the only way to maintain ownership is by copying crap into a parent stack frame.

C/C++ also has long shutdown times, because of a lot of free calls in destructors and malloc managing scheme being inherently inefficient.