this post was submitted on 06 Sep 2024
610 points (90.6% liked)

linuxmemes

20751 readers
594 users here now

I use Arch btw


Sister communities:

Community rules

  1. Follow the site-wide rules and code of conduct
  2. Be civil
  3. Post Linux-related content
  4. No recent reposts

Please report posts and comments that break these rules!

founded 1 year ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 34 points 1 week ago (4 children)

Is it just me or is that more of a hinderance?

[–] [email protected] 15 points 1 week ago (1 children)

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.

[–] [email protected] 5 points 1 week ago (1 children)

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.

[–] [email protected] 2 points 1 week ago

URLs aren't case-sensitive though, so wouldn't those necessarily have another kind of differentiator?

[–] [email protected] 5 points 1 week ago

Definitely an inconvenient thing.

[–] [email protected] 2 points 1 week ago* (last edited 1 week ago)

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