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.
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.)
PowerShell variable names and function names are not case sensitive.
I understand the conventions of using capitalization of those names having specific meanings in regards to things like constants, but the overwhelming majority of us all use IDEs now with autocomplete.
Personally, I prefer to use prefixes anyway to denote that info. Works better with segmenting stuff for autocomplete, and has less overhead of deriving non-explicit meaning from stuff like formatting or capitalization choices.
On top of that, you really shouldn’t be using variables with the same name but different capitalization in the same sections of code anyway. “Did I mean to use $AGE, $Age, or $age here?” God forbid someone come through to enforce standards or something and fuck that all up.
haha that was so infuriating. if their intent was to bastardize the filename horribly to make it noticeable that you defied the DOS limitation, they certainly succeeded. Yuck, totally forgot about the ~1 thing!
Same on macOS. Apple has “case-sensitive HFS+” as an option for UNIX compatibility (or at least they used to) but actually running a system on it is a bad idea in general.
What I wanna know is how are all those breakable objects so close to the edge of the table, and yet still untouched with a cat in the vicinity??? Neither one of you are doing your jobs, lolol!!!
Yeah I agree this isn’t even a meme at all, I get Lemmy is a very political group of people but it’s honestly absurd how people post things everywhere without consideration of the theme
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.
lemmy.world
Oldest