There have been multiple accounts created with the sole purpose of posting advertisement posts or replies containing unsolicited advertising.

Accounts which solely post advertisements, or persistently post them may be terminated.

mrvictory1 ,

Windows and NTFS support case sensitive filenames. The functionality is disabled for compatibility reasons.

Gork ,

I remember the good old days of Windows MS-DOS where they had an 8 character filename limit lol

radamant ,

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

alcoholicorn ,

FlLE.txt FILE.txt

lily33 ,

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.

SpaceCadet ,
@SpaceCadet@feddit.nl avatar

I don’t think there’s a need for File.txt and fILE.txt

It’s not so much about that need. It’s about it being programmatically correct. f and F are not the same ASCII or UTF-8 character, so why would a file system treat them the same?

Having a direct char type to filename mapping, without unnecessary hocus pocus in between, is the simple and elegant solution.

SloganLessons ,

so why would a file system treat them the same?

Because it’s designed for average people, not bots. Imagine the headache of telling people to add a line in file.txt, but they misunderstood and add it to File.txt

Furthermore, I personally cannot think of any use case for having files with the same names reside in the same directory. It would just create confusion even among tech savvy users and programmers

FQQD , (edited )
@FQQD@lemmy.ohaa.xyz avatar

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

poinck ,

Git likes to have a word with you.

wizardbeard ,

Huh, what makes this a use case in favor of case sensitive file names? How does git use this feature?

OrganicMustard ,

Create multiple branches that only differ in cases from a Unix OS so it breaks git for Windows users in the same project.

LouNeko ,

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.

Spider89 ,

FreeCAD?

wildbus8979 ,

KiCAD?

RandomLegend ,
@RandomLegend@lemmy.dbzer0.com avatar

And i hate it being case sensitive

30p87 ,

And I love it.

MudMan ,

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 ,
@RandomLegend@lemmy.dbzer0.com avatar

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 ,

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.

poinck ,

Who sends setup binaries? I would tell my grandma to install it from the repository.

DmMacniel ,
@DmMacniel@feddit.org avatar

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

30p87 ,

For files of casual users it might be of benefit. They don’t care about capitalization. For system files, I find it pretty weird to name them with random capitalization, and it’s actually pretty annoying. Only lower- (or upper-)case would be ok tho.

MudMan ,

Well, camel case does help readability on file names. But I guess that's the point of case insensitive names, it doesn't matter. However you want to call them will work.

huginn ,

CMV: all Linux files should be case insensitive, displayed as lowercase and mandatory snake_case.

SpaceCadet ,
@SpaceCadet@feddit.nl avatar

Even more annoying is that it’s very cumbersome to change the case of a file once you’ve created it.

If you accidentally create fIle.txt when you meant File.txt, the rename function does nothing … and it will keep displaying as fIle.txt. You have to rename it to something else entirely, then rename it back to the original name with the intended case.

Australis13 ,

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

stoy ,

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

SpaceCadet , (edited )
@SpaceCadet@feddit.nl avatar

This isn’t “Windows design”… this is just inherited stone age bullshit from the DOS days when the filesystem was FAT16 and all file names were uppercase 8.3.

JerkyChew ,

You can make windows care about file case sensitivity. We enable it at work to ensure sanity with our local git repo’s. ortussolutions.com/…/how-to-make-windows-folders-…

palordrolap ,

Thought experiment: Would you expect a programming language variable name to be case insensitive?

That is, if you set foo = 1 and then print FOO, what should happen? Most programming languages throw an error.

Is this even comparable with filenames, which are, after all, basically variable names that hold large quantities of data?

If there is a difference, is it the fact it's a file, or - for a mad idea - should files with only a few bytes of data retain case insensitivity? And if that idea is followed through, where's the cutoff? 256 bytes? 7?

(Anyway, Windows filenames are case sensitive, in a sense. If you save "Letter to Grandma.txt" it will retain those two capital letters and all the lower case letters exactly as they are. It won't suddenly change to "LETTER to Grandma.txt", despite the fact that if you try to open a file by that name, you'll get the same file.)

mogoh ,

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

SpaceNoodle ,

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 ,
@AnyOldName3@lemmy.world avatar

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.

Harold_Penisman , (edited )
@Harold_Penisman@lemmy.world avatar

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 ,
@Sonotsugipaa@lemmy.dbzer0.com avatar

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.

raker ,

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

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • [email protected]
  • random
  • lifeLocal
  • goranko
  • All magazines
    •