• DefederateLemmyMl@feddit.nl
    link
    fedilink
    arrow-up
    0
    ·
    edit-2
    2 months ago

    This isn’t “Windows design”… this is just inherited stone age bullshit from the DOS days when the filesystem was FAT16 and all file names were uppercase 8.3.

    NTFS is case sensitive in its underlying design, but was made case insensitive by default, yet case preserving, for reasons of backwards compatibility.

    If Microsoft has to design something from scratch, without the need for backwards compatibility, they go for case sensitive themselves. For example: Azure Blob Storage has case sensitive file names.

    • Redjard@lemmy.dbzer0.com
      link
      fedilink
      arrow-up
      1
      ·
      2 months ago

      If you rename a file only changing the casing it doesn’t update properly, you need to rename it to something else and back.
      This is so userfriendly I have been stumped by it multiple times.

      On the other hand in using Linux I have had a number of problems with the casing of files: The number is 0

      • DefederateLemmyMl@feddit.nl
        link
        fedilink
        arrow-up
        1
        ·
        2 months ago

        If you rename a file only changing the casing it doesn’t update properly, you need to rename it to something else and back. This is so userfriendly I have been stumped by it multiple times.

        To my great surprise, this has been fixed. I don’t know when, but I tried it on my Windows 10 VM and it just worked. Only took them 20 years or so :)