goddamnit

You're viewing a single thread.

134 comments

Semi-related, I'm still salty about Google's rejection of JPEG XL. I can't help but remember this when webp discussion crops up, since Google were the ones who created it.

I still hold hope for JPEG XL and that Google will cave at some point.
- Yes, JPEG XL really is the one that got away. 😭
  Hey Google, 🖕🖕 for killing it, man. Very evil and self-centered choice.
  
  Also I just noticed what the arrow in the image pointed to. Holy crap that would be awful if true.
  
  Yeah, sorry, that part I didn't fact check myself so I didn't even want to mention it. Like I said, many possible reasons.
  
  Ah no worries. I found it a little bit difficult to believe that the decision wouldn't be questioned by the company if it didn't align with its overall goals. That would be weird.
- Not sure what you mean by "Google killed it". JPEG XL proposal was only submitted in 2018 and it got standardized in 2022. It has a lot of features which are not available in browsers yet, like HDR support (support for HDR photos in Chrome on Android was only added 8 months ago, Firefox doesn't support HDR in any shape at all), no browsers support 32 bits per component, there's no support for thermal data or volume data, etc. You can't just plug libjxl and call it a day, you have to rework your rendering pipeline to add all these features.
  I'd argue that Google is actually working pretty hard on their pipeline to add missing features. Can't say the same about Mozilla, who can't even implement HDR for videos for over a decade now.
  
  They removed JPEG XL support from chrome. It was behind a feature flag previously.
  (At least that's what I gathered from reading the screenshot.)
  
  Yeah, why keep a feature which doesn't work? Once they add missing stuff to the renderer, they'll add XL support back. But I guess that will take a few years.
  
  Can you provide a source on how Google is working hard on JPEG-XL missing features?
  
  As I said - photo HDR. Do you even read?
- Just imagine if there was an actual open consortium not spearheaded by monied commercial interests that could temper recent Google decisions. They've lost a lot, if not all, of their goodwill with old guard, open web standards nerds. And the old guard that still actively support their standards influencing schemes now make too much money to stop.

134 comments