this post was submitted on 20 Sep 2025
593 points (82.5% liked)
Programmer Humor
26521 readers
1958 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
And if you already have compression artifacts, what use is lossless?
Only time you would want it is when you are uploading comparison photos specifically showing compression artifacts created from some other compression result.
That's a bit to niche to make it worthwhile.
To further reduce file size without further reducing quality.
There are probably billions of jpeg files out there in the world already encoded in lossy JPEG, with no corresponding higher quality version actually available (e.g., the camera that captures the image and immediately saves it as JPEG). We shouldn't simply accept that those file sizes are going to forever be stuck, and can think through codecs that further compress the file size losslessly from there.
Wait, so lossless webp manages to be smaller than even lossy jpg, while also having to losslessly reproduce jpeg artifacts, which tends to otherwise greatly increase file sizes (as compared to the original lossless file) in lossless formats?
JPEG XL has a mode for losslessly encoding any lossy JPEG into a smaller file size without any loss of quality. Wikipedia has some description of general approaches for losslessly encoding JPEG files further.
I don't know if webp uses any of these tricks, but I don't see why it would be hard to imagine that compression artifacts from a 30-year-old format can be encoded more efficiently today.