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.
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.