this post was submitted on 28 Jan 2025
1599 points (99.6% liked)

Programmer Humor

20176 readers
655 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 2 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 200 points 1 day ago (13 children)

honestly - while a Mac is certainly less painful to use than winshit, putting rubbish files recursively into each(!!) accessed folder, on all thumbdrives ever inserted, that's something Jobs deserves to burn in hell for.

[–] [email protected] 20 points 1 day ago (7 children)

I am not familiar with MacOS, but that seems like a nightmare. What is the purpose of these files?

[–] [email protected] 17 points 1 day ago (1 children)

Iirc they're indexes for the system wide search feature, Spotlight

[–] [email protected] 22 points 1 day ago (2 children)

Is there a valid reason not to store that [[anywhere else]], ideally in Spotlight's data?

[–] [email protected] 2 points 15 hours ago

In Unixy environments like Mac and Linux the application can't always know what the mountpoint of a drive is so it's not always obvious which root folder to put those index/config files in if it's a portable drive or network drive. Some mountpoints are standard per each OS, but not everything sticks to the standard.

[–] [email protected] 9 points 1 day ago

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.

load more comments (5 replies)
load more comments (10 replies)