News for hackers. Stuff that matters.

A comment on Google Revisits JPEG XL in Chromium After Earlier Removal. Parent comment

Re:Google Revisits JPEG XL in Chromium After Earlier Removal by eviks on Sunday November 23, 2025 @10:52AM (#46024437)
> AV2 .... further improve the image compression. ( Edit: Also worth pointing out current JPEG-XL encoder is no where near its maximum potential in terms of quality / compression ratio

But at what cost? From this the en/decoding speed (links below) is much higher for those advanced video codecs, so for various lower powered devices they wouldn't be very suitable?

Also, can we expect "near max potential" with AV2/near future or is it an ever-unachievable goal that shouldn't stop adding "non-max" codecs?

https://res.cloudinary.com/cloudinary-marketing/image/upload...

https://cloudinary.com/blog/time_for_next_gen_codecs_to_deth...

[ Parent | on HN ]
Re:Google Revisits JPEG XL in Chromium After Earlier Removal by jaffathecake on Monday November 24, 2025 @02:15PM (#46037944)
Fwiw, JPEG XL takes around 2.5x the time to decode as an equivalent AVIF, and has worse compression https://jakearchibald.com/2025/present-and-future-of-progres...
[ Parent | on HN ]
Re:Google Revisits JPEG XL in Chromium After Earlier Removal by eviks on Tuesday November 25, 2025 @12:34AM (#46042657)
Interesting, looks like another opportunity for Chrome to avoid the Safari mistake

> slow. There's some suggestion that the Apple implementation is running on a single core, so maybe there's room for improvement.

Though their own old attempt was even worse

> of the old behind-a-flag Chromium JPEG XL decoder, and it's over 500% slower (6x) to decode than AVIF.

[ Parent | on HN ]