jerryX

HEIC is paid, inferior, unpopular ... while JPEG XL is finally the long term replacement of ~30 year old JPEG.

Many smartphones now have 200MP e.g. allowing to crop, in astronomy they count in gigapixels ...

In practice AVIF is made practically only by Google team.

Good summary from https://www.phoronix.com/forums/forum/phoronix/latest-phoron... :

    Max image size is limited to 4K (3840x2160) in AVIF, which is a deal breaker to me. You can tile images, but seams are visible at the edges, which makes this unusable. JPEG XL supports image sizes of up to 1,073,741,823x1,073,741,824. You won’t run out of image space anytime soon.
    JXL offers lossless recompression of JPEG images. This is important for compatibility, as you can re-encode JPEG images into JXL for a 30% reduction in file size for free. AVIF has no such feature.
    JXL has a maximum of 32 bits per channel. AVIF supports up to 10.
    JXL is more resilient to generation loss.5
    JXL supports progressive decoding, which is essential in web delivery, IMO. AVIF has no such feature.
    AVIF is notoriously based on the AV1 video encoder. That makes it far superior for animated image sequences, outperforming JXL in this department by a wide margin. However, JXL also supports this feature.
    AVIF is supported in most major browsers. This includes Chrome (and derivatives) and Firefox (and forks). JXL is supported by almost nobody right now. Only Thorium, Pale Moon, LibreWolf, Waterfox, Basilisk and Firefox Nightly incorporate it. Most of these are community-maintained forks of Firefox. That is a big downside for adoption, as I already ranted about in this post.
    Both formats support transparency and wide gamut (HDR).

Chromium 934 stars, 397 comments: https://bugs.chromium.org/p/chromium/issues/detail?id=117805...

Firefox: 434 upvotes, 61 comments: https://connect.mozilla.org/t5/ideas/idb-p/ideas/status-key/...

Official support software list: https://en.wikipedia.org/wiki/JPEG_XL#Official_support

Comparison/benchmarks: https://cloudinary.com/blog/contemplating-codec-comparisons

Feature comparison: https://jpegxl.info/comparison.png

Like https://en.wikipedia.org/wiki/Library_Genesis

In Chrome it looks identical.

Already in Chrome, Firefox, Edge: https://www.ghacks.net/2021/05/11/find-out-if-your-browser-s...

What virus can be implemented in that?

JPEG XL uses this new ANS coding as e.g. zstd: https://en.wikipedia.org/wiki/Asymmetric_numeral_systems

Zstd uses this new ANS coding: https://en.wikipedia.org/wiki/Asymmetric_numeral_systems

Zstandard uses both Huffman and ANS coding: https://en.wikipedia.org/wiki/Asymmetric_numeral_systems

"Google, over time, went from being a patent sceptic to gradually becoming a patent collector. Now, as we feared, Google becomes patent aggressor. Google is gradually becoming a patent bully now" - that was February 2017.

Now: http://techrights.org/2017/09/11/complaints-about-bad-patent...