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

Programmer Humor

20215 readers
1794 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
[–] gazter@aussie.zone 3 points 1 day ago (1 children)

But do I type 'ImportantFile', or 'importantfile'?

As I understand it, if I searched for either of these strings in a case sensitive file system, I would not find a file called 'IMPORTANTFILE'.

At best, a case sensitive file system makes naming conventions more complex. At worst , it obfuscates files. I just can't imagine a scenario where it would be helpful. Do you really see a need to have a file called 'aaaAaa' and a totally separate one called 'aaAaaa'?

[–] Saleh@feddit.org 1 points 1 day ago* (last edited 1 day ago) (1 children)

The search string is case insensitive. The file name isnt.

So you will find all of them.

[–] Ferk@programming.dev 2 points 9 hours ago* (last edited 8 hours ago) (1 children)

But then you are not getting rid of the complexity, you are just forcing programs to become more complex/inefficient.

I experienced this with the doom libretro core, which is meant to be portable and have minimal dependencies... so if I need it to automatically find DOOM.WAD/ doom.wad/Doom.WAD/etc in a directory I would either have to add a globbing library as dependency to handle this case and have it fetch [Dd][Oo][Oo][Mm].[Ww][Aa][Dd], manually check for each possible case, or list the entire directory (I hope you don't have a library of a million wads!) and compare each file (after upper/lower) just to find the one with the right name. And that could be a real pain for embedded devices with low I/O or if there's a remote storage layer behind.

[–] Saleh@feddit.org 2 points 8 hours ago (1 children)

I think we are looking at this from different angles. I think you are looking at the programmer perspective, and i am looking at the end-user perspective, who uses a GUI file explorer.

In the case of a GUI file explorer the search handles the case insensitivity. So for me using Dolphin in KDE if i have two files:

TEST.txt and test.txt, if i type "tes" on my keyboard, i will be given the uppercase one first. if i type "te" again, it jumps to the next fitting entry, which is test.txt. If i put "test" or "TEST" in the search bar, i will get back both results.

I see why a strictly case insensitive file system makes it easier for programmers down the line to not have to handle the different cases explicitly in their program anymore.

[–] Ferk@programming.dev 1 points 8 hours ago* (last edited 7 hours ago)

Yes, but you know what I did? nothing, I just have the program exclusively accept lowercase doom.wad

This means it became annoying for the user. The problem shifted and now it's the end-user the one with the responsibility to read the manual and do the work. A lot of people just get a DOOM.WAD, put it there and are surprised it doesn't work.

And there are many many programs that are doing the same thing in many similar situations. In fact, in the Linux world, most software pushes this to the end user. So this is just as much of a problem for users as it is for programmers.

At the end of the day, the question should not be: is it more complexity for the user or for the programmer? ..the question should be: what's the end cause making it complex? is there a way it can be made simpler?

This is the same for every problem. Often user-friendliness is a tradeoff, most user-friendly software I've used keeps so much complexity within that it becomes annoyingly slow and inefficient. I'd rather use the terminal for file management than wait for the GUI file browser to finish loading my huge remote storage directories.