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.

Hmm you’re right. I didnt notice so far, nor was it brought up as an issue.

You can activate case sensitivity since Win 10 or so.

The search string is case insensitive. The file name isnt.

So you will find all of them.

Mostly Windows, and construction industry. So projects generate anywhere from a few hundred to up to a hundred thousand files.

Everyone has their own filesystem, and then you often have one formal and multiple informal exchange platforms. You still have people throwing around stuff in E-Mails too.

It is a mess. But in this mess i didn’t come acrosse people complaining they couldnt find a file because of the letters case yet.

I see that it could be different for programmers, but i dont see that apples solution of treating upper and lowercase as identical name is the solution there, rather than working with explicit file naming conventions in the program.

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.

I work with a lot of users and a lot of files in my job.

I don’t remember a single case, where someone had an issue because of upper- or lowercase confusions.

This baby can sequester carbon into layers of 1 mm a year

These values dont necessarily reflect the reality well. Germany has a high retirement age for many European countries, currently at 67 with debates to raise it another 2-3 years. But people who are already 60 cannot change jobs easily, while their companies want to get rid of them.

So in a lot of places they get a deal to do part time, or be legally employed as part time workers, but permanently told to stay home, while getting a reduced salary.

So basically these people are being employed on paper while factually being retired.

Another issue is that manu women are still forced into part time work because there is insufficient daycare available, especially in the affluent and “christian” south, but their husbands incomes dont suffice for full stay at home moms.

Over the past years the average extra hours per employee were around 30 per year, half of them being unpaid.