if you look for a file you type the first letters for the file explorer to jump to the matching name. Retype to jump to the next fitting entry. If you don’t know about this, you can put your string in the search field. If you don’t know about this, you can sort by metadata like file size or date of last change.
It is a non problem.
Also most workplaces tend to develop a file naming convention, either explicitly or implicitly.
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/inefficient.
I experience 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], 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’s assuming the globbing library isn’t already under the hood doing essentially that, which would add significant lag for big directories in low end devices.
if you look for a file you type the first letters for the file explorer to jump to the matching name. Retype to jump to the next fitting entry. If you don’t know about this, you can put your string in the search field. If you don’t know about this, you can sort by metadata like file size or date of last change.
It is a non problem.
Also most workplaces tend to develop a file naming convention, either explicitly or implicitly.
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/inefficient.
I experience 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], 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. And that’s assuming the globbing library isn’t already under the hood doing essentially that, which would add significant lag for big directories in low end devices.