5 ms·

DS Store seems so unfortunate. Yes it serves a purpose. Yes you can work around it in various ways. But the reality is that it’s basically proliferated file lit

DS Store seems so unfortunate. Yes it serves a purpose. Yes you can work around it in various ways. But the reality is that it’s basically proliferated file litter to 99% of people who come across it. It’s uncharacteristically un-Apple in terms of UX polish. Growing up with both System 7.5 / OSX, and windows machines, the Macs never seemed inclined to make me see extraneous files, filetypes, and other “how the computer works” implementation details. It’s just so odd to my mental model of it all to see this file end up everywhere.

DEADMINCE 2y ago
> It’s uncharacteristically un-Apple in terms of UX polish. Apple's polish has always been more about the surface then the internals.
- userbinator 2y ago
  I remember playing around with setting up a Hackintosh, and found all those errors in the system logs --- then realised that an actual working Mac generates much the same (ignorable) errors.
  - plasticeagle 2y ago
    To be fair to Apple here, so does every other operating system. Linux system logs are filled with errors too. In general, keeping the logs of even a moderately complex application "clean" - so that the only errors logged are real errors, in some poorly defined meaning of "real" - is very hard. For operating systems it must be straight up impossible.
    - popcalc 2y ago
      It's difficult to accept as competency when they control both the software and hardware.
    - marcosdumay 2y ago
      > Linux system logs are filled with errors too. Mostly only due to misbehaving hardware. Something that should really not happen on a Mac. And "filled" is way hyperbolic, there usually isn't a lot of it.
al_borland 2y ago
For those who live their whole life within Apple's walls, they will never see .DS_Store files, unless they use the Terminal. Finder (with hidden files shown) doesn't even show them anymore. It is very ugly when files are shared from a Mac to people on Windows though. I think it gives a bad first impression for anyone who might be thinking of transitioning to the Mac.
- nathan_douglas 2y ago
  They pop up in code repositories too, depending on contents and whether the engineer in question noticed it.
  - doomlaser 2y ago
    absolutely essential to add a line for .DS_Store in every .gitignore, unfortunately.
    - klodolph 2y ago
      Enough to teach people to use a global git core.excludesfile, IMO. Same place you should put rules for Emacs / Vim swap files.
      - smix96 2y ago
        Totally correct. Files which are unrelated to the project don't belong in .gitignore.
        account42 2y ago
        It makes sense to add an ignore for .* though and then specifically unignore only those dotfiles/directories that you actully want checked in.
        al_borland 2y ago
        This may be technically correct, and I do have .DS_Store in my global, but I also put it in projects, because I know not everyone on my team is going to do that. I add it to the .gitignore in projects to save me from other people junking up the project. It’s a lot easier to add some lines to a file than it is to micromanage the global file for every potential future contributor.

DEADMINCE 2y ago

> It’s uncharacteristically un-Apple in terms of UX polish. Apple's polish has always been more about the surface then the internals.

userbinator 2y ago
I remember playing around with setting up a Hackintosh, and found all those errors in the system logs --- then realised that an actual working Mac generates much the same (ignorable) errors.
- plasticeagle 2y ago
  To be fair to Apple here, so does every other operating system. Linux system logs are filled with errors too. In general, keeping the logs of even a moderately complex application "clean" - so that the only errors logged are real errors, in some poorly defined meaning of "real" - is very hard. For operating systems it must be straight up impossible.
  - popcalc 2y ago
    It's difficult to accept as competency when they control both the software and hardware.
  - marcosdumay 2y ago
    > Linux system logs are filled with errors too. Mostly only due to misbehaving hardware. Something that should really not happen on a Mac. And "filled" is way hyperbolic, there usually isn't a lot of it.

al_borland 2y ago

For those who live their whole life within Apple's walls, they will never see .DS_Store files, unless they use the Terminal. Finder (with hidden files shown) doesn't even show them anymore. It is very ugly when files are shared from a Mac to people on Windows though. I think it gives a bad first impression for anyone who might be thinking of transitioning to the Mac.

nathan_douglas 2y ago
They pop up in code repositories too, depending on contents and whether the engineer in question noticed it.
- doomlaser 2y ago
  absolutely essential to add a line for .DS_Store in every .gitignore, unfortunately.
  - klodolph 2y ago
    Enough to teach people to use a global git core.excludesfile, IMO. Same place you should put rules for Emacs / Vim swap files.
    - smix96 2y ago
      Totally correct. Files which are unrelated to the project don't belong in .gitignore.
      - account42 2y ago
        It makes sense to add an ignore for .* though and then specifically unignore only those dotfiles/directories that you actully want checked in.
      - al_borland 2y ago
        This may be technically correct, and I do have .DS_Store in my global, but I also put it in projects, because I know not everyone on my team is going to do that. I add it to the .gitignore in projects to save me from other people junking up the project. It’s a lot easier to add some lines to a file than it is to micromanage the global file for every potential future contributor.