> So, what are the forces that have determined the current state of C++?

A subset of the language aimed at library writers. As a user of those libraries all these weirdo features are likely to be transparent.

▲

yosefk 10 hours ago | parent [-]

TFA explains how std::move is tricky to use and this is not a feature reserved for library writers

▲

zabzonk 10 hours ago | parent [-]

Of course it is not reserved for library writers - nothing is. But it is not a feature that application writers should worry about overmuch.

▲

yosefk 10 hours ago | parent [-]

std::move is definitely for there for optimizing application code and is often used there. another silly thing you often see is people allocating something with a big sizeof on the stack and then std::moving it to the heap, as if it saves the copying

	▲	zabzonk 9 hours ago \| parent [-]
		> another silly thing you often see is people allocating something with a big sizeof on the stack and then std::moving it to the heap, as if it saves the copying never seen this - an example?