this post was submitted on 29 Jun 2024
729 points (91.6% liked)
memes
10308 readers
2195 users here now
Community rules
1. Be civil
No trolling, bigotry or other insulting / annoying behaviour
2. No politics
This is non-politics community. For political memes please go to [email protected]
3. No recent reposts
Check for reposts when posting a meme, you can only repost after 1 month
4. No bots
No bots without the express approval of the mods or the admins
5. No Spam/Ads
No advertisements or spam. This is an instance rule and the only way to live.
Sister communities
- [email protected] : Star Trek memes, chat and shitposts
- [email protected] : Lemmy Shitposts, anything and everything goes.
- [email protected] : Linux themed memes
- [email protected] : for those who love comic stories.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the 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.
Why care about JPEG XL?
Because it seems very promising.Rejection?
Google started working on JPEG XL support for chrome, then dropped it despite significant industry support. Apple is also in, by the way.Why do that?
Don't know, many possible reasons. In fairness, even Mozilla hasn't decided to fully invest in it, andlibjxlhasn't defined a stable public API yet.That said, I don't believe that's the kind of issue that'd stop Google if they wanted to push something forward. They'd find a way, funding, helping development, something.
And unfortunately for all of us, Google Chrome sort of... Immensely influences what the web is and will be. They can't excuse themselves saying "they'll work on it, if it gains traction" when them supporting anything is fundamental to it gaining traction in the first place.
You'd have to believe Google is acting in good faith for the sake of the internet and its users. I don't think I need to explain why that's far from guaranteed and in many issues incredibly unlikely.
Useless mini-rant
I really need a single page with all this information I can link every time image standards in the web are mentioned. There's stuff I'm leaving out because writing these comments takes some work, especially on a phone, and I'm kinda tired of doing it.I still hold hope for JPEG XL and that Google will cave at some point.
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.