this post was submitted on 28 Jun 2024
1007 points (97.2% liked)
Technology
59123 readers
2299 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
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
What’s webp and why should I care?
Google’s image format
It’s smaller than png which a company that shows images really likes because it’s cheaper so to force adoption they convert a bunch of images to .webp on google images
The problem is that 1. It hadn’t been adapted anywhere so people would have to convert it back to png to use 2. It is worse in every aspect to jxl files so Google has had to block the adaptation of jxl on the web as much as they can (jxl retains more quality and is half the size of webp)
Currently only webkit browsers support jxl out of the box. Firefox has had it in their nightly builds for years now but have never moved it into standard
If Google wants to push webp because it is smaller than previous formats, and jxl is even smaller than that, why would Google have an interst in blocking jxl?
Not saying Google did not or does not block jxl, just your chain of logic as to why they do that does not make sense to me.
It doesn’t make sense which is why people believe Google has ulterior motives. I haven’t seen any real reason not to use jxl as the new format; but I also haven’t looked that far into it. ¯\(ツ)/¯
JXL is new (like 2 years old), webp is older (> 10 years). Adding support for a thing takes time and resources, which is lower priority when there are good-enough formats already supported.
At least that's my perspective as someone who interacts with product owners (i.e. the type of people deciding what features get prioritized).