Comment

Comment by MadameMinty

Actually I tested it in practical (for me) conditions and that's not necessarily true. Definitely dependent on the content and target environment. https://gist.github.com/MadameMinty/9d2e9a481e955ea55c1bae18...

WebP timing turned out to be true on a few years old tablet, but not on a newer phone nor desktop; the number of large cores determines that time for JXL. The CPU time is probably lower for WebP, didn't measure that. But wall clock tells a different story, and the encode times and size bury WebP.

AVIF is a strange format since its lossy compression can _improve_ when you add a smaller layer; it's smaller than WEBP in the normal modes (s6; s>=7 switches to real-time mode which sucks and s3 takes centuries), sure. But even it decodes faster than WebP in favorable chip conditions. And JXL via Jixel just eats both for breakfast with plenty of room to spare.

parent MadameMinty 11 hours ago

No comments yet

Be the first to share your thoughts.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton