It's 2020 and macOS still uses .DS_Store files 馃槖

Web 17 17 46

@fribbledom where else is it supposed to put its old nintendo handheld consoles?

@fribbledom they JUST made a new file system why didn鈥檛 they just bake folder metadata into that?

@fribbledom so many parts of APFS are baffling to me. Like how it doesn鈥檛 do file parity and supports snapshots yet doesn鈥檛 work with time machine

@fribbledom (doesn鈥檛 work as the backup disk, works fine if it鈥檚 the disk being backed up)

@JarlavGrenlandUpir @fribbledom macOS Death Valley or whatever: the only thing we changed is this hidden file that most people don鈥檛 even know about

To be sure everybody notices who uses Apple, so we poors of Windows and Linux recognize the real masters of the universe when we recibe a folder from a Apple user 馃檮

@Benetako_Arkatiur @fribbledom I鈥檒l never understand why zip utilities and git don鈥檛 just ignore it by default

@cinebox @fribbledom AFS doesn't use them, but network and removal media (which don't tend to be AFS) still do

@cinebox @fribbledom I imagine that should have been possible since forever except when you run on a UFS volume (which nobody does), but I'm not sure. Do directories support multiple forks too? I don't see why they wouldn't.

@cinebox @fribbledom Jokes on you. Even HFS+ had that. But they decided to not use it so that it would survive when you copy to FAT32!

@js @fribbledom thats such a weird choice to make instead of only making .ds_store on incompatible filesystems

@fribbledom and they still manage to get in EVERYTHING. I swear it鈥檚 like the asbestos of the computing world


windows still uses ntfs and drops desktop.ini and thumbs.db in every folder it touches

@Luxotek @fribbledom I wish they'd get rid of the . and .. files too. waste of space if you ask me

Never understood what those were meant to do...

Icon positions. Finder creates them when you browser directories.

I thought they were related to the multiple-fork capabilities of Apple filesystems, but that's the ._* files.

@fribbledom Out of curiosity, what's a more 2020 way to do it?

Are not those files equivalent to .directory files in dolphin?

@jcromero @fribbledom If HFS+ and APFS have support for forked streams on directories too, not just files (and I don't see why they wouldn't, but it might be that they don't), that data could be added in a fork on the directory instead of these breadcrumbs lying around.

I don't know if it's the 2020 thing to do, it's more like a 1991 thing to do. My quick research tells me the classic Mac OSes only produced a FINDER.DAT (and a RESOURCE.FRK) when on MS-DOS media, not on native, so I'm surprised that OSX/macOS made the distinction to avoid ._* files on native (because it can use forked file streams) but still litters the directories with .DS_Store files.
1991 is when System 7 was released and included MultiFinder as part of the OS, but HFS is from 1987.

@fribbledom I haven't used a Mac in a decade and I'm still finding those things all over my NAS

find . -iname ".DS_Store" -exec rename .DS_Store thumbs.db '{}' \;

(PS don't run that, I don't trust my memory, no one else should either)

@fribbledom Welll.... at least it is decentralized? 馃槣

@fribbledom given how they don't really give you full unix access anyway they should just hide them from tools that don't expect it.

@fribbledom doesn鈥檛 Windows 10 still make the hidden thumbs.db file?

@fribbledom I wouldn't care if it weren't for idiots including them in zip files for distribution. What are they, anyway?

@fribbledom I had to start using a Mac for the first time for work and the DS_Store files threw me for a loop.

@fribbledom Of course. MacOS only gets worse over time, never better. Especially with the last few major releases.

Sign in to participate in the conversation

Server run by the main developers of the project 馃悩 It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!