48 karma · joined December 14, 2025
That's my fundamental gripe with C++
int i = 0;
function_0(i,...);
...
function_9(i,...);
which one changes i? It's not obvious in a code review due to default mutable references.
Refuse, reduce, reuse, recyle, rot.
There was just a recent case with Google to decide if they would have to sell Chrome. Of course the Judge ruled no. Nowadays you can have a monopoly in 20 adjacent industries and the courts will say it's fine.
imo corporations have more pull on governments than governments have on businesses at this point as far as long term culture goes.
And worse, in typical C++ fashion, there is still little guaranteed as far as when std::move will actually cause a move. The implementation is still given a lot of leeway. I've been surprised before and you basically have no choice but to check the assembly and hope it continues to be compiled that way as minor changes make their way into the code base.
I spend a lot of time looking at generated assembly and there are some more impressive ones.