• supersquirrel@sopuli.xyz
    1·
    24 days ago

    Where did this art come from? It seems like the cover to a tabletop wargame about the french and indian war or something.

  • FQQD! @lemmy.ohaa.xyz
    1·
    26 days ago

    you should do this with every one of these cases. btw, where does .Trash-1000 actually come from?

  • Lazycog@sopuli.xyz
    1·
    25 days ago

    Hmm… Smells like a windows user aswell… Look at that:

    .desktop desktop.ini

    Edit: fixed the filename

      • Takumidesh@lemmy.world
        1·
        25 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.

        • Kissaki@programming.devEnglish
          11·
          25 days ago

          Case insensitive handling protects end-users from doing “bad” things and confusion.

          • Saleh@feddit.org
            1·
            25 days ago

            I work with a lot of users and a lot of files in my job.

            I don’t remember a single case, where someone had an issue because of upper- or lowercase confusions.

      • Speiser0@feddit.org
        0·
        25 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.

  • kipo@lemm.eeEnglish
    1·
    25 days ago

    Blue Harvest for Mac will continually clean your removable drives of these files.

  • cm0002@lemmy.world
    0·
    26 days ago

    See also: Let’s roll our own .zip implementation that only Mac can reliably read for…reasons

    • stebo@lemmy.dbzer0.com
      0·
      26 days ago

      every time i get a zip file from a mac user it has a folder with random junk in it. what’s up with that? i can open the files without it so clearly those files are unnecessary

      • skuzz@discuss.tchncs.de
        1·
        26 days ago

        Metadata that’s a holdover from the 1980s MacOS behavior. Hilariously, today, NTFS supports that metadata better than Apple’s own filesystems of today. They can hide it in Alternate Data Streams.

          • kalleboo@lemmy.world
            1·
            25 days ago

            APFS still supports resource forks just fine - I can unstuff a 1990’s Mac application in Sequoia on a Apple Silicon Mac, copy it to my Synology NAS over SMB, and then access that NAS from a MacOS 9 Mac using AFP and it launches just fine.

            The Finder just doesn’t use most of it so that it gets preserved in file copies and zip files and such.

  • raspberriesareyummy@lemmy.world
    01·
    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.

      • vvv@programming.dev
        1·
        25 days ago

        the macos file browser, Finder, lets you set a background for a folder, move file icons around to arbitrary positions, other shenanigans. in order for this to work across systems on removable storage media and network mounts, they have this.

          • Natanael@lemmy.zipEnglish
            1·
            25 days ago

            In Unixy environments like Mac and Linux the application can’t always know what the mountpoint of a drive is so it’s not always obvious which root folder to put those index/config files in if it’s a portable drive or network drive. Some mountpoints are standard per each OS, but not everything sticks to the standard.

    • ulterno@programming.devEnglish
      01·
      25 days ago

      You’d want that, but a lot of programs do that, both in Windows and Linux.

      e.g. The .directory files with the [Desktop Entry] spec by freedesktop.org
      Dolphin has the option to enable/disable the feature

      • lengau@midwest.social
        1·
        25 days ago

        FWIW Dolphin only does it if the filesystem doesn’t provide a way to add that metadata directly to the directory and you change the view configuration for that directory away from your standard configuration. Which is how the standard describes to do it. (Some file managers incorrectly add those .directory files to every directory you visit.)

        A mac will add a .DS_Store file to any directory just by breathing on it.