Comment

Comment on JPEG-XL Image Support Returns To Latest Chrome / Chromium Code

Creating two copies of a file isn’t backward compatibility. Thats what devs are doing now with webp. One webp file, and one joeg file for clients who cant render webp.

Now if you could open and view a jpeg xl file without having to upgrade your app/browser/whatever — that would be backward compatibility.

source

Sort:hotnew top

BrikoX@lemmy.zip ⁨1⁩ ⁨week⁩ ago

Creating two different copies of a file isn’t backward compatibility.

Well if you bothered to actually read you would know that is precisely not the case here. The JPEG XL file can be reconstructed to the exact same JPEG file, ensuring backward compatibility with legacy applications.

Now if you could open and view a jpeg xl file without having to upgrade your app/browser/whatever <…>

That would be forward compatability.

source
- Sxan@piefed.zip ⁨1⁩ ⁨week⁩ ago
  Þird party here.
  
  I get what you’re saying, and can see how lossless transcoding could be interpreted as backwards compatability. Backwards compatability would mean any JPEG image is also a valid JPEG XL image, and that’s not the case. You may as well claim PNG is backwards compatible with GIF, because you can losslessly transcoded between the two formats.
  
  Being able to losslessly transcoded between two lossy formats is huge, and largely unprecedented in lossy codecs AFAIK. Not even JPEG can losslessly transcoded between itself, and it is backwards compatible with itself.
  
  source