• RandomLegend [He/Him]@lemmy.dbzer0.com
    link
    fedilink
    arrow-up
    33
    arrow-down
    3
    ·
    2 months ago

    I’m with you here, i find it infuriating and i never ever had the situation where this was beneficial.

    Like who tf actually creates a File.txt, file.txt AND FILE.TXT in one place and actually differentiates them with that.

    • MudMan@fedia.io
      link
      fedilink
      arrow-up
      8
      arrow-down
      3
      ·
      2 months ago

      I mean, it’s less of an issue on Linux for both design and user profile reasons, but imagine a world where somebody can send all the normie Windows users a file called Chromesetup.exe to sit alongside ChromeSetup.exe. Your grandma would never stop calling you to ask why her computer stopped working, ever.

    • macniel@feddit.org
      link
      fedilink
      arrow-up
      4
      arrow-down
      1
      ·
      2 months ago

      Isn’t it less strain on the Filesystem? keeping a sanitised filename next to the actual filename surely has some drawbacks.

    • dev_null@lemmy.ml
      link
      fedilink
      arrow-up
      3
      arrow-down
      1
      ·
      2 months ago

      For example I might store blobs of data processed by my database in files that have the Base64 ID of the blob as the filename. If the filesystem was case insensitive, I’d be getting collisions.

      Users probably don’t make such files, no. But 99% of files on a computer weren’t created by the user, but are part of some software, where it may matter.

      And often software originally written for Linux or macOS and then ported to Windows ends up having problems due to this.