this post was submitted on 19 Oct 2025
42 points (95.7% liked)

Programming

23242 readers
224 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 2 years ago
MODERATORS
snowe@programming.dev
Ategon@programming.dev
MaungaHikoi@lemmy.nz
UlrikHD@programming.dev
42
OpenZL Explained - Changing Data Compression Forever (youtube.com)
submitted 6 days ago* (last edited 6 days ago) by ruffsl@programming.dev to c/programming@programming.dev
20 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] PhilipTheBucket@piefed.social 1 points 4 days ago (1 children)

Let me revise that statement to - it’s better in every metric (compression speed, compressed size, feature set, most importantly decompression speed) compared to all other compressors I’m aware of, apart from xz and bz2 and potentially other non-lz compressors in the best compression ratio aspect.

Your Cloudflare post literally says "a new compression algorithm that we have found compresses data 42% faster than Brotli while maintaining almost the same compression levels." Yes, I get that in some circumstances where compression speed is important, this might be very useful. I don't see the point in talking further in circles anymore, thank you for the information.

[–] phiresky@lemmy.world 1 points 4 days ago* (last edited 4 days ago)

like I said, brotli contains a large dictionary for web content / http which means you can't compare it directly to other compressors when looking at web content. the reason they do a comparison like that is because hardcoded dictionaries are not part of the zstd compression content-encoding because it is iffy.