JPEG XL faces fierce competition from AVIF. And Google. A bit of both0:00 - What is JPEG?1:20 - JPEG XL2:07 - AVIF3:08 - JPEG XL's Strengths4:58 - AVIF Suppo...
People are quick to blame Google for the slow uptake of Jpeg XL, but I don’t think that can be the whole story. Lots of other vendors, including non-commercial free software projects, have also been slow to support it. Gimp for example still only supports it via a plugin.
But if it’s not just a matter of Google being assholes, what’s the actual issue with Jpeg XL uptake? No clue, does anyone know?
“I’m very small minded and am not important or smart enough to have ever worked on a large-scale project in my life, but I will assume my lack of experience has earned me a sense of authority”
-Redisdead
10 whole GB of storage? I understand now why you need such an ultimate compression technology, this is an insurmountable amount of data in these harrowing times where you can buy a flash card the size of a fingernail that can hold that amount about 25 times.
That 0.18mb accumulates quickly on the server’s side if you have 10000 people trying to access that image at the same time. And there are millions it not billions of images on the net. Just because we have the resources doesn’t mean we should squander them…that’s how you end up with chat apps taking multiple gigabytes of RAM.
GIMP supports JPEG XL natively in 3.0 development versions. If I remember correctly GIMP 2.10 was released before JPEG-XL was ready, so I think that’s the reason. They could have added support in smaller update though, which was the case with AVIF.
People are quick to blame Google for the slow uptake of Jpeg XL, but I don’t think that can be the whole story. Lots of other vendors, including non-commercial free software projects, have also been slow to support it. Gimp for example still only supports it via a plugin.
But if it’s not just a matter of Google being assholes, what’s the actual issue with Jpeg XL uptake? No clue, does anyone know?
The issue with jpegxl is that in reality jpeg is fine for 99% of images on the internet.
If you need lossless, you can have PNG.
“But JPEGXL can save 0,18mb in compression!” Shut up nerd everyone has broadband it doesn’t matter
“I’m very small minded and am not important or smart enough to have ever worked on a large-scale project in my life, but I will assume my lack of experience has earned me a sense of authority” -Redisdead
What a dumb comment.
All of that adds up when you have thousands or tens of thousands of images. Or even when you’re just loading a very media-heavy website.
The compression used by JPEG-XL is very, very good. As is the decoding/encoding performance, both in single core and in multi-core applications.
It’s royalty free. Supports animation. Supports transparency. Supports layers. Supports HDR. Supports a bit depth of 32 compared to, what, 8?
JPEG-XL is what we should be striving for.
Check how large your photos library is on your computer. Now wouldn’t it be nice if it was 40% smaller?
I have several TBs of storage. I don’t remember the last time I paid attention to it.
I don’t even use jpeg for it. I have all the raw pics from my DSLR and lossless PNGs for stuff I edited.
It’s quite literally a non issue. Storage is cheap af.
While AVIF saves about 2/3 in my manga downloads (usually jpg). 10 GB to 3 GB. Btw, most comicbook apps support avif.
10 whole GB of storage? I understand now why you need such an ultimate compression technology, this is an insurmountable amount of data in these harrowing times where you can buy a flash card the size of a fingernail that can hold that amount about 25 times.
That was an example, is about a 100 chapter manga. Stop being a jerk.
That 0.18mb accumulates quickly on the server’s side if you have 10000 people trying to access that image at the same time. And there are millions it not billions of images on the net. Just because we have the resources doesn’t mean we should squander them…that’s how you end up with chat apps taking multiple gigabytes of RAM.
It’s competing with webp and it helps prevent jpg artifacts when downloaded multiple times
That’s not how downloading works
If you download and upload repeatedly you potentially lose some data each time which is how we got jpeg memes
that happens when the sites you upload it to re-encode the image
Slightly higher in this thread you spout off complaining about pedantry, and here you are, being even more pedantic?
GIMP supports JPEG XL natively in 3.0 development versions. If I remember correctly GIMP 2.10 was released before JPEG-XL was ready, so I think that’s the reason. They could have added support in smaller update though, which was the case with AVIF.
checks
It doesn’t look like the Lemmy Web UI supports JPEG XL uploads, for one.
Imgur doesn’t let me upload it either, I have to use general file hosts
Removed by mod