Comment

Comment on JPEG is Dying - And that's a bad thing | 2kliksphilip

Legacy client support. Old devices running old browser code can’t support a new format without software updates, and that’s not always possible. Decoding jxl on a 15yo device that’s not upgradable isn’t good UX. Sure, you probably can work around that with slow JavaScript decoding for many but it’ll be slow and processor intensive.

source

Sort:hotnew top

RamblingPanda@lemmynsfw.com ⁨3⁩ ⁨months⁩ ago
But how is that different to any other new format? Webp was no different?

source
- seaQueue@lemmy.world ⁨3⁩ ⁨months⁩ ago
  Google rammed webp through because it saved them money on bandwidth and because they controlled the standard. They’re doing the same thing with jpeg now that they control jpegli. Jpegli directly lifts the majority of features from jpegxl and google controls the standard.
  
  source
ProdigalFrog@slrpnk.net ⁨3⁩ ⁨months⁩ ago
That’s a good argument, and as a fan of permacomputing and reducing e-waste, I must admit I’m fairly swayed by it.

However, are you sure JPEG XL decode/encode is more computationally heavy than JPEG to where it would struggle on older hardware? This measurement seems to show that it’s quite comparable to standard JPEG, unless I’m misunderstanding something.

That wouldn’t help the people stuck on an outdated browser (older, unsupported phones?), but for those who can change their OS, like older PC’s, a modern Linux distro with an updated browser would still allow that old hardware to decode JPEG XL’s fairly well, I would hope.

source
- seaQueue@lemmy.world ⁨3⁩ ⁨months⁩ ago
  Optimized jpegxl decoding can be as fast as jpeg but only if the browser supports the format natively. If you’re trying to bolt jxl decoding onto a legacy browser your options become JavaScript and WASM decoding. WASM can be as fast but browsers released before like 2020 won’t support it and need to use JavaScript to do the job. Decoding webp in JavaScript is, let’s just say it’s not fast and it’s not guaranteed to work on legacy browsers and older machines.
  
  Webp succeeded because Google rammed the format through and they did that because they controlled the standard. You’ll see the same thing happen with the jpegli format next, it lifts the majority of its featureset from jpegxl.
  
  source