4 ms·
It doesn't matter too much (for the web) as you can use <picture> and <source> and specify multiple jxl/avif/webp/jpeg sources, and the browser will choose the
by zebracanevra 5y ago
It doesn't matter too much (for the web) as you can use <picture> and <source> and specify multiple jxl/avif/webp/jpeg sources, and the browser will choose the first type it understands.
These elements are widely supported.
Hopefully JXL doesn't become yet another image format (927)... some features of it are incredible. For example, you can have mixed lossless/lossy content in one image. No longer will you need to choose between a lossy or lossless format: the encoder would intelligently segment the image.
- est31 5y ago> you can have mixed lossless/lossy content in one image. No longer will you need to choose between a lossy or lossless format: the encoder would intelligently segment the image. What's the advantage of that? If I'm dissatisfied with the compression quality in some areas, I can tweak the quality parameter already.
- zebracanevra 5y agoSee https://github.com/libjxl/libjxl/pull/466 https://github.com/libjxl/libjxl/pull/466 for more details. As far as I understand it, the synthetic mode compresses better for (as you can guess) synthetic content. So if you're encoding a mixed content screenshot, you'll get better quality and size by encoding the photos and UI separately.
- est31 5y agoOh I see, that makes sense.