another_another

Aha, so it's not just for the Balmoral Highland Games then?

Actually I do think that's possibly what is happening here.

As you say the Russians aren't amateurs, but at the same time they've massively overstepped their mark this time and have galvanised action against them that possibly didn't particularly have the will before, since they poured a lot of money into platforms that would promote Russia's propaganda (hard and soft).

It seems that currently no amount of money can whitewash what they're doing. Of course that might change again in the future.

> I do my wife's code for her dev job and it honestly works out to like 2 hours a week for me. >She spends maybe 10 hours in meetings

Watch out, if she attends all those productivity sapping meetings, and turns in good code then she'll quickly be promoted to a position that requires no coding. Then that'll be the end of the fun coding :)

>my guess is it would be more comfortable to remain there than to lock down alone in your apartment;

Actually sounds like a good premise for a movie :)

I remember seeing one called 'Arson Fire' which basically conveyed the same thing.

You're right, an atomic inc/dec would also do just fine. I stand corrected.

shared_ptr<> is most useful for multithreaded applications where a pointer can be safely shared amongst many threads, where the last one to go out of scope will call delete on the object.

To do this safely the shared_ptr<> class maintains a reference count which is protected by a mutex. This is pretty inefficient if you never share a pointer across threads.

Better to use unique_ptr<> where the Thing that created it is also the Thing that's responsible for deleting it - after making sure that anything it's shared the pointer with is already safely destroyed (another thread, a collection or some other object).