Elektrine lite

← Feed

@pq1r@tech.lgbt

Post #4272920

2026-07-31 09:07 UTC

@neilmadden@infosec.exchange These tools come from different heritages. ZIP was designed to archive compressed files. Developed in the PC DOS era and came from that mentality - it didn't even have a path for each file, no file permissions. The directory of files is stored at the end of the file, unsuitable for streaming but enables fast random access. Modern versions have paths and per-file encryption. The tar format was designed with the UNIX philosophy, originally for Tape ARchive. Streaming by design, no directory (each file has a small before it, which includes its path and permissions). Files are not compressed - if you want compression you have to pipe the output of tar into a compression utility, something modern tar implementations do themselves. Same with encryption. If your goal is to just compress a folder, both will do a decent job - but try to stream ZIP and you'll hit a wall. Random access in a tar requires going over the entire archive, which can be long. There are use cases for both.

Replies (1)

  • @neilmadden@infosec.exchange 2026-07-31 09:15

    @pq1r@tech.lgbt sure, but for 99.9999% of cases (eg release source downloads on GitHub), the distinctions make no difference. The compression difference is marginal, and pretty much everyone just downloads and unzips the whole thing, doesn’t care about preserving file access times or whatever else. We duplicate storage, processing (eg scanning for vulns) etc to basically just satisfy the fetishes of a few purists IMO.

    Open ##4272918