this post was submitted on 06 Sep 2024
615 points (90.6% liked)

linuxmemes

20880 readers
10 users here now

I use Arch btw


Sister communities:

Community rules

  1. Follow the site-wide rules and code of conduct
  2. Be civil
  3. Post Linux-related content
  4. No recent reposts

Please report posts and comments that break these rules!

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

Yeah, right? Are we pretending that having case sensitive file names isn't a bad call, or...? There are literally no upsides to it. Is that the joke?

[–] [email protected] 29 points 2 months ago (3 children)

I'm with you here, i find it infuriating and i never ever had the situation where this was beneficial.

Like who tf actually creates a File.txt, file.txt AND FILE.TXT in one place and actually differentiates them with that.

[–] [email protected] 5 points 2 months ago (1 children)

I mean, it's less of an issue on Linux for both design and user profile reasons, but imagine a world where somebody can send all the normie Windows users a file called Chromesetup.exe to sit alongside ChromeSetup.exe. Your grandma would never stop calling you to ask why her computer stopped working, ever.

[–] [email protected] 11 points 2 months ago (1 children)

Who sends setup binaries? I would tell my grandma to install it from the repository.

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

Pfft, I would key her the hexdump of the binary via morse code

[–] [email protected] 3 points 2 months ago

Something something emacs

[–] [email protected] 3 points 2 months ago

Isn't it less strain on the Filesystem? keeping a sanitised filename next to the actual filename surely has some drawbacks.

[–] [email protected] 2 points 2 months ago

For example I might store blobs of data processed by my database in files that have the Base64 ID of the blob as the filename. If the filesystem was case insensitive, I'd be getting collisions.

Users probably don't make such files, no. But 99% of files on a computer weren't created by the user, but are part of some software, where it may matter.

And often software originally written for Linux or macOS and then ported to Windows ends up having problems due to this.

[–] [email protected] 5 points 2 months ago (1 children)

For files of casual users it might be of benefit. They don't care about capitalization. For system files, I find it pretty weird to name them with random capitalization, and it's actually pretty annoying. Only lower- (or upper-)case would be ok tho.

[–] [email protected] 9 points 2 months ago

Well, camel case does help readability on file names. But I guess that's the point of case insensitive names, it doesn't matter. However you want to call them will work.