• mrvictory1@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    3 months ago

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

  • stupidcasey@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    3 months ago

    But why though? Do you really want a bunch of file.txt File.txt FILE.txt fIle.txt FiLe.txt FIle.txt flIe.txt… I once had a nasty bug the O in a file name was a 0 and I didn’t notice I can’t imagine the horrors this would cause.

  • Lemzlez@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    3 months ago

    IIRC MySql inherits that behaviour when running on windows (or at least older versions do)

    That was a real fun time when switching OS

  • MehBlah@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    3 months ago

    What I really like is a naming files with a forbidden windows character in Linux and they wont copy over to a windows partition. I end up using a question mark quite a bit for some reason.

  • pyre@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    3 months ago

    thank god it’s not case sensitive holy shit. i don’t understand the kind of person who would see that as a positive.

    • A_Random_Idiot@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      3 months ago

      Seriously.

      It sounds like a fucking nightmare. Imagine working on something for days and it refuses to work cause you accidentally capitalized 1 file name and dont notice it?

      That sounds like the kind of shit they’d do in tech hell.

  • linearchaos@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    3 months ago

    Yeah I’ve been using Linux for a very long time. The amount of time I’ve spent on the case being incorrect is non-trivial. I’ve gotten better at not screwing it up throughout the years but the sum of advantages is far outweighed by the sum of debugging time spent.

  • 9point6@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    3 months ago

    Oh it’s even better, windows explorer can’t really do case sensitive

    But NTFS is a case sensitive file system

    This occasionally manifests in mind boggling problems

  • calcopiritus@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    3 months ago

    I’m with windows on this one. Case insensitive is much more ergonomics with the only sacrifice represented by this meme. And a little bit of performance of course. But the ergonomics are worth it imo.

    • platypus_plumba@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      edit-2
      2 months 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

  • fadhl3y@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    3 months ago

    Strictly speaking, this is a limitation of the default filesystem, and not the core operating system. If you mount a NFS share that is case sensitive, it will still be case sensitive.

    • fatalicus@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      3 months ago

      Technically not a limit there either since you in windows on NTFS can set a flag on a folder to make it case sensitive

      fsutil.exe file queryCaseSensitiveInfo <path>