Upon being awarded the prize of A$10,000 (equivalent to $36,011 in 2022), Young said that he did not know there was a prize and that he felt bad accepting it, as each of the other five runners who finished had worked as hard as he did—so he gave A$3,000 to 41-year-old Joe Record and A$4,000 to the other runners, keeping only A$3,000 for himself.[2] Despite attempting the event again in later years, Young was unable to repeat this performance or claim victory again.[8]

Naah. There is plenty of Gen X, Y, Z who know and plenty of Millenials who dont.

Its just if you wanted to “do stuff with computers” you had to develop some understanding back then.

Today you can “do stuff” like gaming much easier out of the box. So not everyone who “does stuff” knows his way around.

In the office most colleagues of all generations just know how to do their specific things, mostly in MS Office products.

Couldn’t you just handle this with:

breakflag = False

for x in iterator:

     if breakcondition(x):
            breakflag = True
            break  
     dostuff()

Active users does not say how active. E.g. your active users could be less and less, but if 10% leave and the remaining 90% increase their activity by 20%, you end up with an 8% overall increase.

And in winter people stay inside more, so with all these metrics we should probably adjust for seasons.

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.

Plastic recycling can be feasible.

Problems are mixed plastics and like you wrote that it is not economically feasible under current economic conditions.

Reality is that probably your common food packaging should cost 3-10x as much as it does currently, so all plastic packaged food would increase in price by 20-30% or so. (The numbers are just very rough estimates)

The issue is not the recycling, but the lobbying to not create the environment, where it becomes feasible, but plastic packaging becomes less interesting and alternatives become more viable.

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.