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’?
But then you are not getting rid of the complexity, you are just forcing programs to become more complex.
I experience this with the doom libretro core, which is meant to be portable and have minimal dependencies… so if I want to find DOOM.WAD/ doom.wad/Doom.WAD/etc. I would either have to add a globbing library to handle this 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.
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’?
The search string is case insensitive. The file name isnt.
So you will find all of them.
But then you are not getting rid of the complexity, you are just forcing programs to become more complex.
I experience this with the doom libretro core, which is meant to be portable and have minimal dependencies… so if I want to find
DOOM.WAD/doom.wad/Doom.WAD/etc. I would either have to add a globbing library to handle this case, or list the entire directory (I hope you don’t have a library of a million wads!) and compare each file (afterupper/lower) just to find the one with the right name.