213
Browser maker love-in snubs Google-shunned JPEG XL
(www.theregister.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 04 Feb 2024
213 points (87.9% liked)
Technology
59038 readers
3190 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
I'm a photographer; AVIF and WebP do not serve my needs, JPEG-XL does.
I run my own website down to the hardware in my living room; I will not store 5 variations of any 1 picture just so I can serve the best available to clients when JPEG works everywhere and JPEG-XL offers me a lossless transition from JPG to JXL.
Chromium is literally the only reason JPEG-XL isn't being adopted right now, and it's so obvious that Google is pulling those strings.
JPEG-XL Ride or Die.
Two browser orgs.
Not arguing just pointing it out
Mozilla are also dumb, yes, but they aren't the one in control of 90% of the browser marketshare.
There is a difference between indifference and actively working against something.
I saw a web warning saying “if you cant see {x} then consider upgrading to Firefox” today and it fill me with joy
GIF is the future Mr Cameraman
Why do you need to transition from jpeg to anything else? Just keep using jpeg for old files.
That's not a "reason" it's a "decision". Their actual reason is pretty good — they don't want to support every image format that comes along. That's a slippery slope, there are several hundred image formats - should they all be supported? How many of them have security flaws? How much work is it to check for security flaws even if none exist?
The original image formats for the web, jpeg, gif, png, svg, all have major benefits compared to each other. That's why they were successful. There used to be other widely used image formats but they all fell by the wayside because the goal is to try not to have many formats. Ideally we'd only have one.
And WebP moves a long way in that direction, it does basically everything except vector images. AVIF is still around for efficiency reasons (it's very really easy/fast/low battery consumption for camera hardware to create an AVIF).
JPEG-XL has advantages but unlike those two they are really small and not worth the effort.
Converting from jpeg to jxl comes some serious space savings and can be done losslessly.
We change video formats without any major benefits of one over the other. I think it's totally reasonable to do the same with image formats. Especially the data can be losslessly compressed even more.
I wouldn't call speed a major factor for image processing anyway. It's hugely important for movies, where AVIF is coming from, but much less so when there is no hard 30x2160x3840 pixels/s benchmark you need to reach.
And bloat up my codebase with support for a new file extension every 2-5 years? I'll just keep using jpg, then, like the rest of the sane internet, and the format will never die. JXL offered an actual upgrade path, webp and avif doesn't.
Someone is adamant.
They do run a physical machine in their living room for their website… for some reason…