this post was submitted on 06 Sep 2024
614 points (90.4% liked)

linuxmemes

21222 readers
109 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.

  • 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 2 months ago (6 children)

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

    [โ€“] [email protected] 2 points 1 month ago* (last edited 1 month 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

    load more comments (5 replies)