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.