Remember: GNU/Linux and other UNIX systems can make files that are case-sensitive, Windows can't make files that are case-sensitive
Remember: GNU/Linux and other UNIX systems can make files that are case-sensitive, Windows can't make files that are case-sensitive
You're viewing a single thread.
Is it just me or is that more of a hinderance?
I absolutely fail to see the utility of having a user called Bob and bob, or a dir called Downloads and downloads. Capitalisation makes sense in code - at a glance I can know I'm looking at a Class or a var, but for system administration it has only ever wasted time, and not once made anything easier.
If capitalisation is used to indicate the start of words then it could make sense for a webserver to serve ExpertsExchange and ExpertSexChange. But yeah having 16 possible versions of "main" would be horrendous.
URLs aren't case-sensitive though, so wouldn't those necessarily have another kind of differentiator?
Definitely an inconvenient thing.
Yeah
I honestly don't get why everyone is agreeing with Windows on this one. I just love how explicit Linux is.
file.txt is fucking file.txt. Don't do any type extra magic. Do exactly as I'm saying. If I say "open file.txt", it is "open file.txt", not "open File.txt".
The feature isn't being able to create filenames with the same name, nobody does that. The feature is how explicit it is.
It would be so confusing to read some code trying to access FILE.TXT and then find the filesystem has file.txt