News for hackers. Stuff that matters.
Re:FSF Slams Google over Dropping JPEG-XL in Chrome by GuB-42 on Sunday April 16, 2023 @10:54AM (#35590522)
The problem is that old PNG and JPEG are good enough for most purposes. They are certainly not as efficient but with todays technology and bandwidth, there is little downside to using JPEG and you know it will be supported everywhere.

It is not the case for video. Video is still a huge bandwidth hog, and finding better codecs is worth it, that's why they get better support. Webp is a clever hack as it is essentially a single frame webm video, so if you have webm support, which is worth it, then you can have webp almost for free, JPEG-XL doesn't have that incentive.

Re:FSF Slams Google over Dropping JPEG-XL in Chrome by kevin_thibedeau on Sunday April 16, 2023 @02:52PM (#35593129)
Webp max resolution is 16383 x 16383. That is a problem in some applications.
Re:FSF Slams Google over Dropping JPEG-XL in Chrome by selcuka on Sunday April 16, 2023 @07:40PM (#35595200)
Why any modern image spec should have a maximum resolution is beyond me.
Re:FSF Slams Google over Dropping JPEG-XL in Chrome by jonas21 on Sunday April 16, 2023 @10:55PM (#35596373)
WebP is based on VP8, which is a video format. Video formats can have maximum resolutions to make it easier to implement hardware decoders.
Re:FSF Slams Google over Dropping JPEG-XL in Chrome by flangola7 on Monday April 17, 2023 @02:08AM (#35597312)
What application? That's 8x 8K or 32x 4K. Even theoretical futuristic giant displays would not need that.
Re:FSF Slams Google over Dropping JPEG-XL in Chrome by jerryX on Monday April 17, 2023 @03:10AM (#35597627)
Many smartphones now have 200MP e.g. allowing to crop, in astronomy they count in gigapixels ...
Re:FSF Slams Google over Dropping JPEG-XL in Chrome by flangola7 on Tuesday April 18, 2023 @02:17AM (#35610546)
A 200MP smartphone is a nonsensical idea, their lenses are not big enough to utilize that many pixels. Even if it was actually possible, that 200MP is getting auto compressed the moment you message or upload it anywhere. I'm asking about legitimate uses.
Re:FSF Slams Google over Dropping JPEG-XL in Chrome by enlyth on Sunday April 16, 2023 @03:13PM (#35593309)
Agreed, PNG and JPEG already serve most purposes.

JPEG = I want to see the content in the image but don't care too much about the quality

PNG = I want a lossless version of this image

Since bandwidth is cheap in most places, the only advantage that JPEG XL has is suddenly not that enticing.

Re:FSF Slams Google over Dropping JPEG-XL in Chrome by exmadscientist on Sunday April 16, 2023 @03:32PM (#35593490)
It's not just that. There are purposes that require JPEG and so if I get a WEBP or AVIF or JXL I am actively angry.

I was trying to set the desktop background image on a project laptop last week. I found an image I liked, that would immediately remind me what machine this was when I look at it.

It was an AVIF. Windows 10 won't accept those as desktop backgrounds. It looked, for all intents and purposes, like the search image results were going to give me JPEGs -- the URL ended in .JPG and had "jpeg" as the media type! -- but that is not what I got. This did not work. Refusing to give up, I eventually determined that using curl to retrieve the image gave me a usable JPEG, and so I got my background and now I can tell this stupid project laptop apart.

For my use cases, which is as someone who does light work with images (backgrounds, occasional use in some kind of paint program, occasional insertion into documents or slides), anything that isn't a JPEG or PNG is actively harmful. Not everyone uses images the way I do, but developers need to remember that not everyone is a passive sheep who just stares at things or a power-developer who builds JPEG-XL from source in their sleep. There are people in between, and we don't take kindly to being forgotten.

Re:FSF Slams Google over Dropping JPEG-XL in Chrome by jemmyw on Sunday April 16, 2023 @06:57PM (#35594967)
We shouldn't use a new format because some website sent you the wrong mime type and you don't know how to use an image converter? By that logic we should still be using .bmp files for all images.
Re:FSF Slams Google over Dropping JPEG-XL in Chrome by selcuka on Sunday April 16, 2023 @07:42PM (#35595208)
I believe the main point is that Windows doesn't support AVIF desktop backgrounds, which is annoying. PNG and JPG (and possibly GIF) are common denominators for a vast majority of systems and applications.
Re:FSF Slams Google over Dropping JPEG-XL in Chrome by exmadscientist on Sunday April 16, 2023 @07:51PM (#35595244)
The main point is that nothing supports AVIF other than browsers, and one or two image manipulation programs. If I have to open up GIMP every time I want to insert an image into a document, we have lost.
Re:FSF Slams Google over Dropping JPEG-XL in Chrome by sroussey on Sunday April 16, 2023 @08:37PM (#35595509)
Every apple device supports AVIF natively and by default.
Re:FSF Slams Google over Dropping JPEG-XL in Chrome by olyjohn on Tuesday April 18, 2023 @05:00PM (#35620077)
I guess that's great if you own an Apple device?
Re:FSF Slams Google over Dropping JPEG-XL in Chrome by pasabagi on Monday April 17, 2023 @01:40AM (#35597187)
$ convert yourfile.avif yourfile.jpg
Re:FSF Slams Google over Dropping JPEG-XL in Chrome by exmadscientist on Monday April 17, 2023 @04:05AM (#35597973)
How much time does that waste, every single time I have to interact with these? How much quality does it lose?

Face it, these "modern" image formats are a massive annoyance for everyone except Web engineers.

Re:FSF Slams Google over Dropping JPEG-XL in Chrome by pasabagi on Monday April 17, 2023 @04:42AM (#35598198)
... so different formats exist because people want different things out of images, for instance for print, or for web, or for editing, and because all compression algorithms have their own tradeoffs. That's not a web engineer thing.

I can't really imagine a world where you don't have to choose what format files should be in, and I can't really imagine a more easy way to do that conversion.

Re:FSF Slams Google over Dropping JPEG-XL in Chrome by jemmyw on Monday April 17, 2023 @06:08AM (#35598768)
I don't know that much about the subject but I had an image for a website I was optimising and the avif version was 10x smaller than the png version, even after I'd run through the normal techniques to squeeze it down, and 3x smaller than the jpeg while still looking much better. That's a really significant saving.

Making an image your wallpaper isn't something people do every day, going through an extra step is hardly onerous. And support will increase until it no longer matters.

Re:FSF Slams Google over Dropping JPEG-XL in Chrome by afavour on Sunday April 16, 2023 @09:36PM (#35595902)
Certainly it is annoying. But it’s a very poor reason to continue using an inefficient codec.