I think it turned into some amount of shit slinging that stopped being relevant to the shit at hand. I’m guessing mods decided to close that sphincter before the verbal diarrhea overflowed the rim of the post ¯\_(ツ)_/¯
I think it turned into some amount of shit slinging that stopped being relevant to the shit at hand. I’m guessing mods decided to close that sphincter before the verbal diarrhea overflowed the rim of the post ¯\_(ツ)_/¯
The poop knife is irrelevant until and unless one plans to flush, which this question did not ask.
Also, why do you assume the nurse is a lady?
I’d like to think there is a strategist in her camp who urged Biden to stay in for as long as he did, and only swap out after the first debate, closer to the 3 month runway mark. And that strategist is just waiting until after the election to gloat publicly about the scheme.
Now that’s a conspiracy theory I can get behind.
In my utopia, Google would be forced to continue to pay out the current annual contract sum, at a decreasing percentage every year, for some number of years, to all affected companies, giving them the opportunity to divest and pivot.
The root problem doesn’t get fixed if the company with enough money to be a monopolist still has the money when this is “resolved.”
https://en.m.wikipedia.org/wiki/Nuclear_fusion
The fusion of light elements up to a certain nucleus size releases energy. However, fusion only occurs at very high temperatures and pressures. The goal is to 1) create the conditions for nuclear fusion (which they did), 2) have the fusion reaction produce energy that sustains those conditions (they did for 48 seconds), and ideally a tiny bit more, 3) gather residual energy that isn’t critical to the reaction itself, which is the part that looks like a steam engine.
Give https://ploum.net/2023-06-23-how-to-kill-decentralised-networks.html a read. Might sway you, might not.
If dropping a database scares you, you are either unaware of the disaster recovery process, or there isn’t one. Edumacate yourself, or the org, as appropriate, so as to increase your confidence when dropping databases.
Maybe. There are many ways to move files and directories around without using Finder, at which point all indexed data about those files and directories will be stale. Forcing something as core as
mv
to update Spotlight would be significantly worse, I think. By keeping the.DS_Store
files co-located with the directory they index, moving a directory does not invalidate the index data (though moving a file without using Finder still does). Whether retaining indexing on directory moves is a compelling enough reason to force the files everywhere is probably dependent on whether that’s a common enough pattern among workflows of users, and whether spotlight performance would suffer drastically if it were reliant on a central store not resilient against such moves.So, it’s probably a shaky reason at best.