• atx_aquarian@lemmy.world
    link
    fedilink
    arrow-up
    0
    arrow-down
    1
    ·
    edit-2
    5 months ago

    Fun fact, though: Linux is the only case-sensitive one.

    Edit: I feel silly for forgetting that it’s all about the choice of FS. If anyone needs anything from me, I’ll be in the corner, coloring.

    • Localhorst86@feddit.org
      link
      fedilink
      arrow-up
      0
      ·
      5 months ago

      From a technical standpoint, the windows NTFS filesystem is designed inherently case sensitive, just windows doesn’t allow creating case sensitive files.

      Connecting an NTFS drive to linux, you can create two separate files readme.txt and Readme.txt.

      Using windows, you can see both files in the filesystem, but chances are most (if not all) software will struggle accessing both files, opening readme.txt might instead open Readme.txt or vice versa.

        • The_Decryptor@aussie.zone
          link
          fedilink
          English
          arrow-up
          1
          ·
          edit-2
          5 months ago

          NTFS was designed back in the mid 90s, when the plan was to have the single NT kernel with different subsystems on top of it, some of those layers (i.e. POSIX) needed case sensitivity while others (Win32 and OS/2) didn’t.

          It only looks odd because the sole remaining subsystem in use (Win32) barely makes use of any of the kernel features, like they’re only just now enabling long file paths.

      • Honytawk@lemmy.zip
        link
        fedilink
        English
        arrow-up
        1
        ·
        5 months ago

        But why? What is the point?

        That you can give 2 different files the same name? Because that would confuse the hell out of every regular user. Especially if you work on a network share and have an entire directory full of same named files because everyone and their grandma throws their files in there.

        It is almost as bad as Case Sensitive Usernames and email.