Remember: GNU/Linux and other UNIX systems can make files that are case-sensitive, Windows can't make files that are case-sensitive

LouNeko , 11 minutes ago

That would be awful for CAD software since they often display part names, which are derived from the file name only in uppercase letters for readability. But Linux doesn’t really have any industry standard CAD software anyway.

raker , 1 hour ago

I throw that at every party for years now and they still don’t get it.

FQQD , 1 hour ago (edited 43 minutes ago)

It’s neat that Linux has the ability to do this, but I honestly can’t think of a good usecase for this. I think this is more confusing than it is useful

radamant , 1 hour ago

Windows way is superior, in my opinion. I don’t think there’s a need for File.txt and fILE.txt

alcoholicorn , 1 hour ago

FlLE.txt FILE.txt

lily33 , 28 minutes ago

Indeed. Linux audio allows control characters like backspace to be part of a file name (though it is harder to make such file as you can’t just type the name). Which is just horrible.

Australis13 , 1 hour ago

This is one case where I think Windows is appropriately designed for its target audience.

stoy , 15 minutes ago

I don’t really see the benefit of allowing users to create files with the same name in the same directory, yeah, yeah I know that case sensitivity means that it isn’t same name, but imagine talking to a user, guiding them to open the file /tmp/doc/File and they open /tmp/doc/file instead

Harold_Penisman , 1 hour ago (edited 1 hour ago)

What a tragedy. Giving files slightly different names seems far more organized and logical than having several files with the same name and different capitalization. Really seems like a non-issue to me.

Sonotsugipaa , 55 minutes ago

I’ve used Windows for a bit more than a decade, and I only found out its VFS is case-insensitive (by default) after I fully ditched the OS, when a bunch of Electron applications created directories with different cases - nothing ever broke because of it, save for a single Godot game.

Personally, I think case-insensitivity seldom makes sense, though I’m also aware that not everyone [knows how / is able] to properly operate a keyboard.

mogoh , 2 hours ago

To my knowledge since Windows 10, files can be case sensitive. It is still tricky to setup, but it won’t break.

SpaceNoodle , 1 hour ago

Nah, Windows still fucks it up. I was forced to use Windows 11 for a code generation tool from a chip vendor the other week and it screwed everything up by inserting references to a directory with different cases than how it was actually created.

AnyOldName3 , 3 minutes ago

That’s more likely to be the tool assuming it’s running on a case-insensitive filesystem than it is Windows breaking anything. If you mount networked storage running on a case-sensitive machine, that’s something that’s worked fine in Windows for a very long time.

RandomLegend , 2 hours ago

And i hate it being case sensitive

30p87 , 1 hour ago

And I love it.

MudMan , 1 hour ago

Yeah, right? Are we pretending that having case sensitive file names isn't a bad call, or...? There are literally no upsides to it. Is that the joke?

RandomLegend , 1 hour ago

I’m with you here, i find it infuriating and i never ever had the situation where this was beneficial.

Like who tf actually creates a File.txt, file.txt AND FILE.TXT in one place and actually differentiates them with that.

MudMan , 1 hour ago

I mean, it's less of an issue on Linux for both design and user profile reasons, but imagine a world where somebody can send all the normie Windows users a file called Chromesetup.exe to sit alongside ChromeSetup.exe. Your grandma would never stop calling you to ask why her computer stopped working, ever.

DmMacniel , 1 hour ago

Isn’t it less strain on the Filesystem? keeping a sanitised filename next to the actual filename surely has some drawbacks.