Completely agree, and will definitely make that change. As soon as Panera Bread starts selling Chunks.
Completely agree, and will definitely make that change. As soon as Panera Bread starts selling Chunks.
I find that system inconvenient, as it does not inform me of how I should eat any given item. Classification for the purpose of classification is insufficient. However, an alternative that allows me to prepare my ustensils based on the classification is useful, and therefore I propose…
Soup, salad, and sandwich are the three states of food, and they can go through phase transitions. They are closely accompanied by spoon, fork, and knife, respectively.
A soup is any food that requires a spoon, and thus includes soups, drinks, cereal with milk, etc. Tipping a container is merely the use of the container as a large and unwieldy spoon, a straw is similarly a spoon when its topology is combined with suction.
A salad then is anything bite sized that can be forked, and one’s hands are little more than fleshy forks, the fingers prehensile tines. Popcorn, salads, cut up steak bites, a handful of cheerios, etc.
A sandwich is anything that requires it to be cut in order to be consumed, and one’s incisors are merely built-in knives. A sandwich is thus the vast majority of the cube rule’s content, and only because the cube rule focuses on the physical location of the starch. This is, of course, entirely irrelevant when it comes to the consumption of food.
To observe a phase transition, one can cut up a sandwich without consuming it, thereby turning it into a salad; can drown a salad to turn it into a soup; can freeze a soup to turn it into a sandwich, etc.
Shredded cheese is a salad.
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.
Post office too. Really any government office where the public is allowed inside.
Underpaid workers trying to explain bureaucratic minutiae (for which they are not responsible) every single day to people who are not versed in that minutiae, do not want to learn it, cannot learn it, and are preemptively frustrated that they have to have this interaction in the first place. There is no winning–mental health isn’t cheap, do the workers’ resilience only lasts for so many years/months/days before they default to hating the clients, and the clients don’t trust publicly available instructions, thus dooming themselves to the shitty interactions.
The only way to fix this is to take both people out of the equation–preprocess everything that might need to happen for everyone, to the point of turning every transaction into a single trasaction. That requires for every city, county, state, national, international agency to federate, so that you never have to file multiple documents to do a thing.
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.