4 ms·
I don't know why HN is so obsessed with this particular image format. Adding image formats on the web has a really high maintainability cost and there is a fair
by bawolff 3y ago
I don't know why HN is so obsessed with this particular image format. Adding image formats on the web has a really high maintainability cost and there is a fairly reasonable argument that it wasn't worth it in this case.
- jeroenhd 3y agoIt's better WebP, without patents and license fees (so unlike HEIC). There are also advantages to encode and decode speeds compared to other formats. It's a superior format compared to most alternatives in many situations. Adding the format and maintaining it requires some work, but the potential for load speeds and data savings is huge. It's also finally a somewhat efficient format for bitmap animations after all these years of GIF and APNG. I've also run into the 16k size limit while converting some PNGs to WebP myself, to JPEG XL would be a nice way to losslessly compress those images more efficiently as well. That said, so far WebP is serving me fine in most cases, I don't really care if it takes two weeks or two years for JPEG XL to make it into the mainstream.
- pornel 3y agoIt doesn't matter that it's better than WebP, because that isn't the alternative. The alternative that browsers have shipped is AVIF. JPEG XL's advantage over AVIF is less significant. It's not a clear win, but diminishing returns and nice-to-have features vs AVIF's wider deployment and head start in AV1 implementations.
- padjo 3y agoIt’s a litmus test for some people of how much google is turning into 90s era Microsoft
- jsnell 3y agoThe analogy makes no sense, given JPEG XL was primarily created by Google. That's what makes the reaction so strange. If JPEG XL had been enabled by default in Chrome instead of removed, would HN be happy? Or would we be up in arms about how Google is trying to force yet another image format on the browser ecosystem?
- lonjil 3y agoJPEG XL is a collaboration between a team at Google Research Zurich and Cloudinary. AVIF is no small part developed by Chrome developers. Treating Google as a unified monolith doesn't make any sense. It's perfectly possible for Chrome to behave like 90s Microsoft and for the Googlers in Zurich to do completely different things.