Re:The JPEG XL Image Coding History, Features, Coding Tools,...
by jandrese on Tuesday July 15, 2025 @11:57AM
(#44572511)
Sadly removing support from Chrome is effectively the same as killing it off. And the reason is Google wants people to use webp instead.
[ Parent
| on HN ]
Re:The JPEG XL Image Coding History, Features, Coding Tools,...
by greenavocado on Tuesday July 15, 2025 @01:14PM
(#44573507)
Friendly reminder that WebP is trash https://www.youtube.com/watch?v=w7UDJUCMTng
Re:The JPEG XL Image Coding History, Features, Coding Tools,...
by can16358p on Tuesday July 15, 2025 @02:06PM
(#44574100)
While I'm not the biggest fan of WebP, using generation loss as a metric wouldn't be an indicator of a real world scenario. I can't think of any actual instance where an image needs to be re-encoded, say, 10 times, let alone 100+ times.
Re:The JPEG XL Image Coding History, Features, Coding Tools,...
by greenavocado on Tuesday July 15, 2025 @02:17PM
(#44574240)
What do you think happens to images shared and re-shared between people online?
Re:The JPEG XL Image Coding History, Features, Coding Tools,...
by OneDeuxTriSeiGo on Tuesday July 15, 2025 @03:17PM
(#44574821)
Not really? Chrome dropped support but Google is actually supporting the JPEG-XL rust port that Firefox is waiting on.