Might depend on your file browser.

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?

I have not.

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

Will re-word post.

I also use arch, btw, so yes I’m probably biased in a similar way as you.

Most FOSS software I downloaded is very friendly to me, thanks. Or do you have a particular unfriendly FOSS software in mind?

Btw, out of interest, if the software you use is so unfriendly to you, why do you use it? Money reasons?

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.

Possible. For me, the things I see from windows (disclaimer: I haven’t used any dos since years, but I’ve occasionally seen video material (including, for example, menus with ads, and horribly confusing settings)) are obtuse, and FOSS stuff is normal. But I may be biased in the a different direction than you.

There seems to be some confusion. With user friendliness I wasn’t referring to the UI. See Edit in updated post.