Here are the 3 most prevalent themes from the Hacker News discussion:
1. Inconsistent Browser Support for JPEG XL
The discussion reveals that JPEG XL support is highly fragmented across different browsers and versions, creating a fragmented user experience. While WebKit-based browsers (like Safari and Orion) generally support the format, Chromium and Firefox implementations vary significantly. Users report the format works in specific forks like Zen, Waterfox, or LibreWolf, but often fails in the standard releases of Chrome or Firefox.
nine_k: "Chromium 143 (the latest available in Void Linux, a rolling-release distro) still can't. The chrome://flags/#enable-jpegxl-image-format is not even found in the build :("
capitainenemo: "Checking the Firefox bugs on this, it seems they decided to replace the C++ libjxl with a rust version which is a WIP, to address security concerns with the implementation. All this started a few months ago."
cdmckay: "That’s because it uses the WebKit renderer built in to iOS"
2. The Detrimental Impact of the "JPEG XL" Name
There is a strong consensus that the naming choice was unfortunate and confusing. The name "JPEG XL" implies a large or heavy file size ("XL"), which contradicts the format's efficiency goals. Critics argue that associating with the older JPEG brand also reminds users of low-quality compression artifacts, making the format unappealing to the general public.
unglaublich: "I think JPEG XL's naming was unfortunate. People want to associate new image formats with leanness, lightness, efficiency."
crazygringo: "Honestly, that's exactly what it sounds like to me too... it's just way too many letters total. When we have 'giff' and 'ping' as one-syllable names, 'jay-peg-ex-ell' is unfortunate."
flexagoon: "I feel like 'jpeg' has generally become a shorthand for 'low quality compressed digital picture'"
3. Technical Comparison and Performance Debates (JPEG XL vs. AVIF)
The conversation frequently pivots to comparing JPEG XL against its main competitor, AVIF. While proponents argue that JPEG XL is the superior "universal" format due to its handling of high-quality images and progressive rendering, others point out that AVIF currently has better browser support and hardware decoding integration. The debate highlights a tension between the theoretical superiority of JPEG XL and the practical adoption reality of AVIF.
judah: "I was also surprised to see that, in Safari, JPEG XL takes 150% longer (as in 2.5x) to decode vs an equivalent AVIF... I thought that 'fast decoding' was one of the selling points of JPEG XL over AVIF, but now I'm not so sure."
uyzstvqs: "JPEG XL is also good, but why not use AVIF? It's widely supported by browsers, and rivals JPEG XL in being the best lossy image format."
F3nd0: "Because JPEG XL is the first format to actually bring significant improvements across the board. In some aspects AVIF comes close, in others it falls far behind, and in some it can’t even compete."