I'm 'using punctuation in a filename feels wrong' years old.

[jimfl@hachyderm.io]

@alicemcalicepants I’m “I knew I was dreaming, because the filenames had more than 8 characters” years old

[sjcooke66@mastodon.social]

@frauxirah @catselbow @alicemcalicepants @piiabartos

[peterludemann@mathstodon.xyz]

@glueckstein @alicemcalicepants
I remember 6.3 (DEC RADIX 50)

[davefischer@hachyderm.io]

@alicemcalicepants

Anyone "just tell me which track I'm allocated" old?

[bodling@deacon.social]

@alicemcalicepants Do the kids out there even get what this is all about?

[disorderlyf@todon.eu]

@alicemcalicepants Wait, you can do that?

[pauamma@mstdn.social]

@alicemcalicepants "filenames have 2 components 8 characters or shorter each" years old here. (Extra credit question: is that older or younger?)

[alicemcalicepants@ohai.social]

@pauamma I definitely remember the eight-character limit, but I gladly accepted the change to being allowed longer names

[disorderlyf@todon.eu]

@bit @alicemcalicepants tbf I'm pretty sure most Windows installs still treat filename.txt and FILENAME.txt as the same file.

[apz@some.apz.fi]

@alicemcalicepants Sometimes when I watch backup job reports I can't but sigh when I see people not understanding the concept of file names and creating typing something like "this could be for Martin.... or John..... .docx".

Don't get me started on how to this day it's such a hassle when non-ASCII letters are in file names and then there's supposed to be some inter-operating system sharing of it. You never know what actually happens.

Sometimes it's even inside the same OS, like a case where there was a file called something like "bearing flange ⌀ 25mm.something" and the program that had created it could not open it when you double clicked it from Windows's file manager, but they could open it by going FIle -> Open in the program.