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.
Programmer Humor
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
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
You'd want that, but a lot of programs do that, both in Windows and Linux.
e.g. The .directory
files with the [Desktop Entry]
spec by freedesktop.org
Dolphin has the option to enable/disable the feature
FWIW Dolphin only does it if the filesystem doesn't provide a way to add that metadata directly to the directory and you change the view configuration for that directory away from your standard configuration. Which is how the standard describes to do it. (Some file managers incorrectly add those .directory files to every directory you visit.)
A mac will add a .DS_Store file to any directory just by breathing on it.
today I learned - using Linux at home since 2005ish and I have never had an auto-file generated on any USB attached drives of mine...
I am not familiar with MacOS, but that seems like a nightmare. What is the purpose of these files?
the macos file browser, Finder, lets you set a background for a folder, move file icons around to arbitrary positions, other shenanigans. in order for this to work across systems on removable storage media and network mounts, they have this.
Iirc they're indexes for the system wide search feature, Spotlight
Nope, that's the .Spotlight-{INDEX} folder which is also often created 😁
Is there a valid reason not to store that [[anywhere else]], ideally in Spotlight's data?
See also: Let's roll our own .zip implementation that only Mac can reliably read for....reasons
every time i get a zip file from a mac user it has a folder with random junk in it. what's up with that? i can open the files without it so clearly those files are unnecessary
Metadata that's a holdover from the 1980s MacOS behavior. Hilariously, today, NTFS supports that metadata better than Apple's own filesystems of today. They can hide it in Alternate Data Streams.
Hmm.. Smells like a windows user aswell.. Look at that:
~~.desktop~~ desktop.ini
Edit: fixed the filename
System Volume Information
... You mean desktop.ini?
Ah shit I've forgotten the ancient tablets, ill fix that thank you!
I've caught the whiff of some Linux too...
lost+found
Thumbs.db
you should do this with every one of these cases. btw, where does .Trash-1000 actually come from?
Freedesktop.org’s trash specification. It’s where files moved to trash go before being deleted when it’s emptied. The 1000 is the user id.
.Trash-999 was already taken by a metal band.
I had a long and frustrating conflict with this, on this post.
As @d_k_bo@feddit.org (An dem Punkt könnten wir auch einfach Deutsch labern) noted, it's a freedesktop.org specification.
I still stand the point that it's not very thought through (a hidden dir? Why?), and that blindly implementing it is annoying. It shouldn't be a universal standard for all systems, as it's only relevant if you use a file manager which can then use that dir as Trash dir - which I don't. That could be tested by only allowing filemanagers to create the dir, and if it doesn't exist, discard the data. That's probably how some programs work, as only Prismlauncher has created the dir.
Workaround: ln -s .Trash-1000 /dev/null
…and whoever decided a file system should be case insensitive by default, I hate you.
What's the use case for case sensitive file names
Well an uppercase ASCII char is a different char than its lowercase counterpart. I would argue that not differentiating between them is an arbitrary rule that doesn't make any sense, and in many cases, is more computationally difficult as it involves more comparisons and string manipulations (converting everything to lower case).
And the result is that you ultimately get files with visually distinct names, that aren't actually treated as distinct, and so there is a disconnect from how we process information and how the computer is doing it.
'A' != 'a', they are just as unequal as 'a' and 'b'
Edit: I would say the use case is exactly the same as programming case sensitivity, characters have meaning and capitalizing them has intent. Casing strategies are immensely prevalent in programming and carry a lot of weight for identifying programmers' intent (properties vs backing fields as an example) similar intent can be shown with file names.
Think the other way around: What's the use case for case insensitive file names? Does it justify the effort and complexity for the filesystem and the programs to know the difference between lower and upper space chars?
What’s the use case for case insensitive file names?
Human comprehension.
Readme, readme, README, and ReadMe are not meaningfully different to the average user.
And for dorks like us - oh my god, tab completion, you know I mean Documents, just take the fucking d!
The moment when you try to rename a folder in windows from Hello to hello and it doesn't work.
I would also like a word with “bonjour” process while we’re at it.
Thought it was a virus when I first discovered it.
no one? Ok
Would you have felt differently if it was called Rendezvous?
Probably not. I know better then to trust the french /s
Every fucking folder in the file share has one of these
Found one of these in the firmware zip file of my soundbar today.
defaults write com.apple.desktopservices DSDontWriteNetworkStores -bool TRUE
Helps a bit.
__MACOSX folders hither and yon.
Just gitignore that. Same for dot idea and whatever vscode adds, if anything
I am not exactly a programmer. What is the .DS_Store file for?
Kind of a mac's version of desktop.ini. Remembers layouts and other metadata about a folder.
As much as they love to sue people, I don't understand why Nintendo doesn't go after Apple for trademark infringement, so that they're forced to finally come up with a better method of storing folder attributes.