1. Apple’s “faithful archive” philosophy
Apple deliberately preserves macOS‑specific metadata (Finder info, resource forks, Gatekeeper tags, etc.) when creating tarballs, treating them as a way to keep the original filesystem semantics intact.
"From Apple's perspective, this is the way to preserve Finder / Gatekeeper / metadata semantics." – LatencyKills
2. Annoyance with hidden macOS artifacts
Many users are frustrated by the proliferation of invisible files like .DS_Store, .fseventsd, and other “garbage‑dump” attributes that clutter archives and can be unintentionally included.
"never seeing another .DS_Store should be a system‑wide option!" – taftster
3. Work‑arounds and portable‑tar strategies
The practical fix is to suppress the extra metadata when creating archives—using the COPYFILE_DISABLE environment variable or tar options such as --no-xattrs/--no-mac-metadata. This lets users produce clean, cross‑platform tarballs without the surprise of hidden attributes.
"setting the COPYFILE_DISABLE=1 env variable would disable the inclusion of macOS‑specific metadata." – LatencyKills