.DS_Store - eviltoast
  • supersquirrel@sopuli.xyz
    2·
    15 小时前

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

  • raspberriesareyummy@lemmy.world
    2049·
    2 天前

    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.

    • ulterno@programming.devEnglish
      471·
      2 天前

      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
        441·
        2 天前

        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.

        • ulterno@programming.devEnglish
          91·
          2 天前

          Well, those are different specifications. Apple(who wants everything for themselves) vs FDO(whose main goal seems to be interoperability)

        • ulterno@programming.devEnglish
          2·
          2 天前

          I have manually made .directory files (using a bash script) to set icons on folders.

          It feels good when programs let you know what they intend on doing.

      • vvv@programming.dev
        50·
        2 天前

        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.

          • filcuk@lemmy.zip
            2·
            1 天前

            I don’t think the code is available for people to figure out whether there’s a reason or if it’s completely arbitrary.

          • Natanael@lemmy.zipEnglish
            2·
            2 天前

            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.

          • FearfulSalad@ttrpg.network
            9·
            2 天前

            Maybe. There are many ways to move files and directories around without using Finder, at which point all indexed data about those files and directories will be stale. Forcing something as core as mv to update Spotlight would be significantly worse, I think. By keeping the .DS_Store files co-located with the directory they index, moving a directory does not invalidate the index data (though moving a file without using Finder still does). Whether retaining indexing on directory moves is a compelling enough reason to force the files everywhere is probably dependent on whether that’s a common enough pattern among workflows of users, and whether spotlight performance would suffer drastically if it were reliant on a central store not resilient against such moves.

            So, it’s probably a shaky reason at best.

        • TedZanzibar@feddit.ukEnglish
          1·
          15 小时前

          Were you talking about MacOS? It’s been a long time since I last had to use it but I assumed it was case sensitive because it’s Unix based. Uh maybe ignore me then!

          • moseschrute@lemmy.world
            1·
            15 小时前

            Yeah. They have both case sensitive and case insensitive options when you format your drive. It used to default to case insensitive. I haven’t formatted my boot drive in a long time, so I can’t say what it defaults to today.

      • Takumidesh@lemmy.world
        592·
        2 天前

        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
          4·
          2 天前

          is exactly the same as programming case sensitivity

          Me working on a case insensitive DB collation 🤡🚀🐱‍🏍

        • gazter@aussie.zone
          45·
          1 天前

          If I have four files, a.txt, A.txt, b.txt, and B.txt, in what order do they appear when I sort alphabetically?

          edit: I don’t understand why this was downvoted?

              • gazter@aussie.zone
                7·
                2 天前

                So if someone tells me to look for a file amongst a long list, I need to look in two different areas- the uppercase and lowercase areas.

                I get why it’s more technically correct to differentiate, but from the perspective of a human user, it’s a pain in the ass.

                • Ferk@programming.dev
                  1·
                  16 小时前

                  I’m with you, and not just from a “human” perspective. Also when writing small programs meant to be relatively lean/simple it can be a problem when the user expects it to find a particular file regardless of its case (will it be DOOM.WAD or doom.wad? Doom.wad? Doom.WAD? … guess it’ll have to be [Dd][Oo][Oo][Mm].[Ww][Aa][Dd] and import some globbing library as extra dependency… that, or list the whole directory regardless its size and lower/upper every single filename until you find a matching one…)

      • moseschrute@lemmy.world
        111·
        2 天前

        On Mac when I rename a folder from “FOO” to “foo” git sees them as the same folder so no change is committed. In JavaScript I import a file from “foo” so locally that works. Commit my code and someone else pulls in my changes on their machine. But on their machine the folder is still “FOO” so importing from “foo” doesn’t work.

  • cm0002@lemmy.world
    1281·
    2 天前

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

    • stebo@lemmy.dbzer0.com
      701·
      2 天前

      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
        691·
        2 天前

        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
            5·
            2 天前

            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.

  • Lazycog@sopuli.xyz
    1068·
    2 天前

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

    .desktop desktop.ini

    Edit: fixed the filename

  • kipo@lemm.eeEnglish
    7·
    2 天前

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

    • M.int@lemm.ee
      8·
      1 天前

      This seems like a bit of a scam:
      On your external drives you can prevent the creation of .DS_Store

      defaults write com.apple.desktopservices DSDontWriteNetworkStores -bool true
defaults write com.apple.desktopservices DSDontWriteUSBStores -bool true

      If you really want to continuously delete DS_Store from both your internal and external hard drives you can set up a cronjob:

      15 1 * * * root find / -name '.DS_Store' -type f -delete
    • katy ✨@lemmy.blahaj.zone
      9·
      2 天前

      When I had a Mac, literally the first thing I did was set up a Hazel rule to delete every single .DS_Store in every folder.

  • webghost0101@sopuli.xyz
    612·
    2 天前

    I would also like a word with “bonjour” process while we’re at it.

    Thought it was a virus when I first discovered it.

    • tyler@programming.dev
      1·
      8 小时前

      Isn’t bonjour the reason that devices like printers famously worked so much better on Mac than windows? I feel like I read an article about that like a decade or two ago.

    • JackbyDev@programming.devEnglish
      161·
      2 天前

      Idk what all it does and doesn’t do, but installing it in Windows lets you find your Raspberry Pi by its “.local” hostname. I know it was originally for printers or something.

      • boonhet@lemm.ee
        13·
        2 天前

        It’s for local service discovery. Those services may be printers on your network, or another computer sharing music on iTunes (which is why as a Windows user you’d usually get Bonjour when installing iTunes). Or maybe it’s your Raspberry Pi.

        It feels iffy because it comes bundled with other software without you being asked (IIRC) and it autoruns on startup. And I mean 20 years ago when iPods were a thing and people had to use iTunes on Windows, a couple dozen megabytes of RAM really mattered too. Hell I had 512 MB back when I had an iPod (and therefore iTunes)

    • MonkderVierte@lemmy.ml
      3·
      2 天前

      That was what caused duplicates on setting the printer as default on dad’s PC. Just disable active scanning for new printers in the config. Was quite some detective work with examining the service file and recursively grepping /etc for variable names multiple times.

    • M.int@lemm.ee
      1·
      1 天前

      Don’t forget:

      defaults write com.apple.desktopservices DSDontWriteUSBStores -bool true
      • M.int@lemm.ee
        9·
        2 天前

        Why is there a * in front of DS_Store?
        Seems like fastly made a small mistake find . -name '.DS_Store' -type f -print -delete would just match the exact file and is faster.

  • boonhet@lemm.ee
    281·
    2 天前

    Just gitignore that. Same for dot idea and whatever vscode adds, if anything

      • boonhet@lemm.ee
        14·
        2 天前

        It’s not, but I still prefer not pushing my config on others, or others pushing theirs on me.

    • andioop@programming.devEnglish
      10·
      2 天前

      git add . > git commit -m "initial" > git push

      Later when I git status or just look at the repo online… “oh crap I let .DS_Store in didn’t I…” and then I remember to set up a .gitignore and make a new commit to take out the .DS_Store and put in the .gitignore.

      • PartiallyApplied@lemmy.world
        5·
        2 天前

        You probably already know this, but for those who don’t, git can globally ignore patterns. It’s the first thing I set up after logging in. Honestly wish git just shipped this way out of the box (maybe match .DS_Store by name and some magic bytes?) with a way to disable it. Just for the sake of easier onboarding

    • JackbyDev@programming.devEnglish
      91·
      2 天前

      Use this so that the things you need to share do get shared.

      .idea/*
!.idea/codeStyles
!.idea/runConfigurations

.vscode/*
!.vscode/settings.json
!.vscode/tasks.json
!.vscode/launch.json
!.vscode/extensions.json
!.vscode/*.code-snippets

      Note: I haven’t checked the vs code ones in depth, the list might not be perfect.

      • kora@sh.itjust.works
        152·
        2 天前

        I personally strongly advise against committing IDE junk to version control. Assuming your IDE workspace defaults are “sane” for the rest of the contributors is not a good practice.

        • JackbyDev@programming.devEnglish
          42·
          2 天前

          If your whole team uses the same IDE, what’s wrong with commiting things like run configurations and code styles? I agree in general, but a wholesale ban on it is very cargo culty to me. There can be legitimate times to do it.

          • kora@sh.itjust.works
            72·
            2 天前

            I elaborated on it below. Your team will grow and shrink. No guarantee that each developer will bring the same IDE. This is especially true for open source projects.

            If it works your team, no need to be dogmatic about it. Just be careful about what you put there and agree on a set of sane defaults with your team. Your project should build and run tasks without needing a specific IDE.

          • Eager Eagle@lemmy.worldEnglish
            31·
            2 天前

            Absolutely nothing wrong. Their whole argument is that it delivers no guarantees about the things set in these files, but setting these presets is more about convenience than enforcing an equal development environment.

            Whoever needs to enforce things like formatting and linting at the project level should be using a CI step.

            • JackbyDev@programming.devEnglish
              12·
              2 天前

              Sure, fail the entire build because of a formatting problem. Hey, wouldn’t it be cool if we could stop that from happening? I don’t know, maybe by also adding in IDE specific formatting files? No? Oh. I wasn’t aware we could only have formatting files OR a CI format checker. 🙄

              None of these things come at the expense of others. You can do both. Even if it’s part of the local build process I’d much rather know in my editor than on the terminal. And you may say “just have everyone do the same setup” to which I’d wonder what sort of magical land you live in where everyone always follows those rules and/or you can get buy in from management to spend that much time bike shedding and why you’d prefer either of them to just adding the damn file to version control to avoid it entirely.

      • Eager Eagle@lemmy.worldEnglish
        31·
        2 天前

        .vscode doesn’t store cache or any trash like that, so if you’re including all settings, tasks, etc, you can probably just include everything.

        The only thing to keep in mind is to only add settings, extension recommendations, etc that apply to all your collaborators and aren’t just personal preferences. A few good examples are formatting rules, task definitions to run the project, and linting rules that can’t be defined somewhere else.

        • kora@sh.itjust.works
          63·
          2 天前

          Linting rules and scripts should never live in an IDE-specific directory. I should not need to know your IDE configuration to run scripts and lint my files.

          I have yet to come across a language that requires configuration to be stored that way. All modern languages have separate configuration and metadata files for use cases you have defined.

          As for workspace defaults, whatever IDE configuration works for you is not guaranteed to work for others. Shoving extension suggestions down their throat each time IDE is booted should not be a part of your source code, as IDE extensions should not be needed to run your code.

          • brian@programming.dev
            3·
            2 天前

            linting config itself wouldn’t be defined there, and it would be verified in ci and such, but a setting to tell vscode which linter and extension it should use to show warnings would be.

            modern languages may have their own way for configuration but they don’t have a way to bind it to the list of vscode tasks and define how to run a debugger, which is the part that gets stored.

            it’s easy to go overboard with extension suggestions, but I don’t think adding an extension for linter used, extension for formatter used, and any languages used if there’s a definitive extension.

            My team is split between visual studio, vscode, and I use emacs. we have config for both vs and vscode in our repos since it makes working on a new project so much nicer and means we aren’t just sharing editor configs through side channels instead. it doesn’t do anything to me if I have editor config for an IDE I don’t use in the repo, but it makes it easier for someone new to jump in with a sort of same environment immediately

          • Eager Eagle@lemmy.worldEnglish
            31·
            2 天前

            Can we stop with the absolutes?

            It’s okay to commit IDE config if your team uses mostly one editor.

            It’s also okay to include extension recommendations. While extensions may not be needed to run the code, depending on the editor and language they’re highly desirable. It’s that kind of extension that should be recommended. I’m sure there’s a setting to disable them if, for some reason, the editor keeps asking you.

          • dev_null@lemmy.ml
            1·
            2 天前

            Linting rules and scripts should never live in an IDE-specific directory.

            Of course they should. Obviously it shouldn’t be the only place they are, but committing IDE code styles settings that match the externally-enforced project styles is absolutely helpful.

            Or, in our project we have a bunch of scripts that you can run manually, but we also have commited IntelliJ run configurations that make running them a convenient in-IDE action.

          • JackbyDev@programming.devEnglish
            11·
            2 天前

            Linting rules and scripts should never live in an IDE-specific directory. I should not need to know your IDE configuration to run scripts and lint my files.

            This is what I’m getting at with it being cargo culty. You can have generic scripts and also IDE specific run configurations too.