Gzipped Tarball - !!link!!

| Feature | .tar.gz | .zip | |--------|-----------|--------| | Preserves Unix permissions | ✅ Yes | ❌ No (ignores execute bits, symlinks) | | Streamable | ✅ Yes (tape/pipe friendly) | ❌ Needs central directory at end | | Open standard | ✅ Fully | ⚠️ Partially (some extensions proprietary) | | Compression ratio | ✅ Very good (DEFLATE) | ✅ Same algorithm | | Random access | ❌ Painful | ✅ Possible |

But gzip cannot pack multiple files. Give it a directory, and it says: “No, thanks.” gzipped tarball

So why not just use a ZIP file? Because tar preserves Unix file attributes (symlinks, hard links, device files, executables) in a way ZIP never quite got right. It’s the native “archive” format of the Unix world. | Feature |

gunzip -c myfolder.tar.gz | tar -xf - This is in action. Two tools, each doing one thing well, combined into a powerhouse. 🔄 Part 3: Why Not Just Use ZIP? ZIP does both: archiving + compression. So why does the open-source world still love .tar.gz ? It’s the native “archive” format of the Unix world

So the classic Unix pipeline was born:

For sharing photos with Windows friends? Use ZIP. Here’s a party trick:

For source code, system backups, and Docker layers, .tar.gz wins because it faithfully restores the original environment.