• raspberriesareyummy@lemmy.world
    0·
    26 days ago

    honestly - while a Mac is certainly less painful to use than winshit, putting rubbish files recursively into each(!!) accessed folder, on all thumbdrives ever inserted, that’s something Jobs deserves to burn in hell for.

      • Speiser0@feddit.org
        0·
        26 days ago

        Think the other way around: What’s the use case for case insensitive file names? Does it justify the effort and complexity for the filesystem and the programs to know the difference between lower and upper space chars?

        • Reddfugee42@lemmy.worldEnglish
          1·
          2 days ago

          The use case for case insensitive file names is all of history has never cared about what case the letters are in for a folder with someone’s name or a folder with an address or a folder for a project name.

          Use case for case insensitive file names is literally all of history. All of it.

      • Takumidesh@lemmy.world
        0·
        26 days ago

        Well an uppercase ASCII char is a different char than its lowercase counterpart. I would argue that not differentiating between them is an arbitrary rule that doesn’t make any sense, and in many cases, is more computationally difficult as it involves more comparisons and string manipulations (converting everything to lower case).

        And the result is that you ultimately get files with visually distinct names, that aren’t actually treated as distinct, and so there is a disconnect from how we process information and how the computer is doing it.

        ‘A’ != ‘a’, they are just as unequal as ‘a’ and ‘b’

        Edit: I would say the use case is exactly the same as programming case sensitivity, characters have meaning and capitalizing them has intent. Casing strategies are immensely prevalent in programming and carry a lot of weight for identifying programmers’ intent (properties vs backing fields as an example) similar intent can be shown with file names.