You may also want to try, for example, the files "a1", "a2", "a3", and "a10". Lexicographically, "a2">"a10", but my file browser displays "a10" after "a2".
Think the other way around: What's the use case for case insensitive file names? Does it justify the effort and complexity for the filesystem and the programs to know the difference between lower and upper space chars?
It seems you're right. I wasn't aware that it has a definition. https://en.wikipedia.org/w/index.php?title=Userfriendliness As a result, I was so naive to just use it as being friendly to users.
I'm kinda surprised that this seems to be a well established term (as can be seen by so many here interpreting it with this definition).
Proprietary shit is always easier to work with, if you’re just wanting the most basic thing that software does.
Do you have examples?
My image viewer shows images, my pdf viewer shows pdfs, my file browser shows files, my music player plays music files, and so on. All of them can do a little more, but the basic functionality is just there usually.
I can see the reflection of spicy tuna in his hungry eyes.