this post was submitted on 13 Jul 2023
632 points (99.4% liked)
Asklemmy
43945 readers
638 users here now
A loosely moderated place to ask open-ended questions
Search asklemmy ๐
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- !lemmy411@lemmy.ca: a community for finding communities
~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Because zstd is not mature enough. Facebook claimed it was production stable, yet even with 1.5.1 it created corrupt archives at level 16 or above compression. Moreover, zstd is a single file compressor which means it needs a container for all files (like TAR) before initiating compression. I benchmark and observe zstd apart from blosc and many other projects aiming for Pareto frontier, however I find it quite concerning nobody thinks about Pareto frontier in terms of distribution of compressed contents, since compression is only performed once.
7Z is a full featured stable general purpose archival format with more than 25 years of development and track record, and has support for repairable headers, Unix/Windows precision timestamp support, far stronger compression (10-20% better ratio than zstd) and incredible ease of access (7-Zip on Windows and compress/decompress support built into Linux distributions).