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++.

>>26
It's stdlib that is not using move constructors, dipshit.  C++ copies everything by default because it is a shit language, and your gay bear club of ``serious men'' is nothing but a circlejerk of uglies who love to memoize annoying details of their basic instruments.