News for hackers. Stuff that matters.
Re:Shipping JPEG XL in Chrome by sylware on Wednesday October 07, 2026 @07:48AM (#49991423)
I thing the endgame is lossless PNG with 16bit color components with basic compression like gzip or at best bzip2. Or a format without the weirdness of PNG 'line based loading' which is obsolete nowdays. The "expensive part", apart from the compression algorithm, being the meta data storage without kludge.
Re:Shipping JPEG XL in Chrome by pmarreck on Wednesday October 07, 2026 @08:21AM (#49991753)
I believe 7zip outdoes bzip2 these days along every metric

And lossless jpeg-xl exceeds your idea

Re:Shipping JPEG XL in Chrome by ciupicri on Wednesday October 07, 2026 @11:16AM (#49994008)
7zip meaning what, LZMA (xz)?
Re:Shipping JPEG XL in Chrome by pmarreck on Wednesday October 07, 2026 @11:21PM (#50001568)
Yes
Re:Shipping JPEG XL in Chrome by dist-epoch on Wednesday October 07, 2026 @11:29AM (#49994221)
and zstandard outdoes 7zip (LZMA)
Re:Shipping JPEG XL in Chrome by pmarreck on Wednesday October 07, 2026 @11:21PM (#50001569)
not in compression density, I don't believe, but yeah, along most other metrics
Re:Shipping JPEG XL in Chrome by apopapo on Wednesday October 07, 2026 @07:54AM (#49991480)
These days I favour lossless WEBP instead of PNG. I often save around 30%~40% of file size compared to PNG, especially when the PNG is encoded with lots of bits per pixel (i.e 48 bits or 24 bits).
Re:Shipping JPEG XL in Chrome by F3nd0 on Wednesday October 07, 2026 @10:35AM (#49993459)
I think that’s why they were advocating for gzip or bzip2 instead of just relying on PNG’s built-in compression.
Re:Shipping JPEG XL in Chrome by sylware on Friday October 09, 2026 @06:44AM (#50018661)
PNG compression is zlib (deflate)
Re:Shipping JPEG XL in Chrome by mrob on Wednesday October 07, 2026 @07:57AM (#49991504)
>without the weirdness of PNG 'line based loading' which is obsolete nowdays

How? Line-based loading is a very simple way to exploit 2D spatial coherence. A 1D format like gzip loses this advantage for minimal gain in simplicity.

Re:Shipping JPEG XL in Chrome by groundzeros2015 on Wednesday October 07, 2026 @12:34PM (#49995153)
You can’t just ignore signal compression algorithms unless you are fine allocating 4-5x more bandwidth to images.
Re:Shipping JPEG XL in Chrome by sylware on Friday October 09, 2026 @06:37AM (#50018601)
With lossless compression and the "modern" internet, it is a matter to indeed allocate more to image bandwidth, from an internet point of view, that would be the price of 'end game' image format quality (lossless and 16bits per component).

You are missing critical metrics: the absolute values which are now very important in our super high speed internet and beyond powerfull consumer hardware.

It is a bit like linux on steam: 6%... but millions, ratio is little, but the absolute is so huge that it you cannot ignore anymore their market value (like macOS though).

Re:Shipping JPEG XL in Chrome by atomicthumbs on Wednesday October 07, 2026 @05:05PM (#49998786)
how about lossless JPEG XL
Re:Shipping JPEG XL in Chrome by sylware on Sunday October 11, 2026 @04:49AM (#50041029)
defeat the whole purpose of simplicity, runtime and SDK.
Re:Shipping JPEG XL in Chrome by Broiler9437 on Wednesday October 07, 2026 @10:56PM (#50001456)
16bit PNG is simply too inefficient. If you care about high bit depth, JXL has vastly higher 32 bit ceiling with superior compression
Re:Shipping JPEG XL in Chrome by sylware on Friday October 09, 2026 @06:50AM (#50018702)
From a panel point of view, this is "end game": for a color component, you can get one discret color component value per line/column. Color banding is gone with a good panel in sRGB on large chunk of the panel with very gradient oriented image data.