I’m with you, and not just from a “human” perspective. Also when writing small programs meant to be relatively lean/simple it can be a problem when the user expects it to find a particular file regardless of its case (will it be DOOM.WAD or doom.wad? Doom.wad? Doom.WAD? … guess it’ll have to be [Dd][Oo][Oo][Mm].[Ww][Aa][Dd] and import some globbing library as extra dependency… that, or list the whole directory regardless its size and lower/upper every single filename until you find a matching one…)
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’?
A computer will spit out A, B, a, b
See also: ASCII chart
So if someone tells me to look for a file amongst a long list, I need to look in two different areas- the uppercase and lowercase areas.
I get why it’s more technically correct to differentiate, but from the perspective of a human user, it’s a pain in the ass.
I’m with you, and not just from a “human” perspective. Also when writing small programs meant to be relatively lean/simple it can be a problem when the user expects it to find a particular file regardless of its case (will it be
DOOM.WADordoom.wad?Doom.wad?Doom.WAD? … guess it’ll have to be[Dd][Oo][Oo][Mm].[Ww][Aa][Dd]and import some globbing library as extra dependency… that, or list the whole directory regardless its size andlower/upperevery single filename until you find a matching one…)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.