176

But hey, at least everyone supports webp now. (lemmy.world)

submitted 5 months ago by renzev@lemmy.world to c/memes@lemmy.world

36 comments fedilink hide all child comments

Context: Even though Chromium has native support for AVIF, a very nice image format, Microsoft goes out of their way to remove it from Edge, which is a chromium fork. Jpeg XL (JXL) (not to be confused with Jpeg (JPG) or Jpeg 2000 (jpg2k) ) is another nice image format, which, IIRC, is only supported in Firefox.

top 36 comments

sorted by: hot top controversial new old

[-] renzev@lemmy.world 21 points 5 months ago

Discussion thread: What's your favourite image format and why?

[-] pineapplelover@lemm.ee 58 points 5 months ago

Png because it's lossless and pretty universal. Svg is pretty cool because it's vectorized but it's also a pain to make good svg.

[-] aeronmelon@lemmy.world 8 points 5 months ago

Still waiting for animated PNG. It would make it the perfect universal compressed image format.

[-] mlg@lemmy.world 6 points 5 months ago

Animated PNG actually does exist but it has poor support coverage.

I remember using it to make whatsapp animated stickers

[-] lud@lemm.ee 5 points 5 months ago* (last edited 5 months ago)

All major browsers (98% of all users) have supported APNG since at least 2020

Firefox: 2008.
Safari: 2014.
Chrome: 2017.
Edge: 2020.

https://caniuse.com/apng

I believe the photo app in Win 10 (and maybe 11) still doesn't support it but that shouldn't hinder web devs.

[-] pineapplelover@lemm.ee 2 points 5 months ago

I didn't even know that was a think. That would be hella cool.

[-] TxzK@lemmy.zip 18 points 5 months ago

WebP cause small size, can be transparent, can be animated, can use either loseless and lossy compression. Also it pisses of many people which is funny to me.

[-] drkt@feddit.dk 28 points 5 months ago* (last edited 5 months ago)

If you want to piss people off, support JPEG XL

Every time you mention it, ~~Google shills~~ WebP supporters come out of the woodworks to do their song and dance!

[-] renzev@lemmy.world 2 points 5 months ago* (last edited 5 months ago)

I''m working on a website right now, trying to choose which image format to use. I think I'm gonna store both webp and AVIF versions on the server, and have Javascript figure out which format is best for the browser automatically (for images that have to be loaded with Javascript anyway).If I have time, I might even try detecting if JXL is supported via third-party extension and using that too.

[-] drkt@feddit.dk 6 points 5 months ago* (last edited 5 months ago)

have Javascript figure out which format is best for the browser

Please don't- HTML has native image fallback functionality https://www.w3schools.com/TAGS/tag_picture.asp

edit

lemmy swallowed my codeblock, take this instead

https://stackoverflow.com/questions/71719254/correct-way-to-display-an-img-fallback

edit

[-] renzev@lemmy.world 3 points 5 months ago

Thanks for the info! I was already suspecting that this could be done without JS, just didn't know how.

[-] renzev@lemmy.world 6 points 5 months ago

The pissing people off part is why I post all my memes in webp haha

[-] TxzK@lemmy.zip 3 points 5 months ago

Extremely based

[-] cloudless@feddit.uk 11 points 5 months ago

Gif because its correct pronunciation is gif.

[-] aeharding@lemmy.world 6 points 5 months ago

JXL. Better compression in my testing and better quality. Also very flexible format with JPEG compatibility

[-] psvrh@lemmy.ca 6 points 5 months ago

Encapsulated Postscript, because I like my images Turing-complete.

[-] renzev@lemmy.world 1 points 5 months ago

Do you write postscript by hand? I once got the change to take a postscript programming class, but sadly I didn't (I wish I did tho). How does it compare with SVG? I know SVG has a lot of limitations (for example, you can't change the color of a shape filled with a pattern), so I guess eps' turing completeness lets you overcome things like that, since you can just program in whatever functionality you need?

[-] JigglySackles@lemmy.world 4 points 5 months ago

Any of them that don't have drm schemes in them.

[-] gens@programming.dev 3 points 5 months ago

Now BC7 because i'm playing with graphics programming. Usually... png i guess because it's simple.

[-] mvirts@lemmy.world 16 points 5 months ago

Let's rename JXL to GPEJ to give GIF pronunciation a run for its money

[-] renzev@lemmy.world 8 points 5 months ago* (last edited 5 months ago)

When it comes to pronunciations of obscure computer acronyms, my favourite is btrfs (the filesystem), because I've never seen anyone advocate for any specific pronunciation, not even the devs/official documentation. Bee Tree Eff Ess? Bee Tee Arr Eff Ess? Butter Eff Ess? Better Eff Ess? Whatever bloats your goat!

[-] AnIntenseMoist@lemmy.world 4 points 5 months ago

butt terfs

[-] rigatti@lemmy.world 15 points 5 months ago

I was excited for JXL... is it dead dead?

[-] swooosh@lemmy.world 4 points 5 months ago

N. Just google removed it from chromium. I can view jxl on android, so it's not dead. And samsung S24 (iirc) will use jxl to save pictures

[-] Wistful@discuss.tchncs.de 9 points 5 months ago

What would it take for JXL to become supported and more widespread? Who even uses it currently?

[-] Lojcs@lemm.ee 18 points 5 months ago

Someone needs to make a website that uses jxl heavily then contact a journalist about a weird website they found that opens 10x faster in safari vs chrome

[-] renzev@lemmy.world 3 points 5 months ago

I said it in another comment, but I'm actually working on a website right now, which happens to lazy-load a lot of images with Javascript. I think I'll store all the images in webp, avif, and JXL formats, and have the javascript code automatically load the one which is supported by the browser. Hopefully if it takes off, it can promote support for modern image formats!

[-] vbb@lemmy.world 1 points 5 months ago

WebKit has support for it (used in Safari and Epiphany). Last time I checked firefox didn’t have support. There is an issue in chromium bug tracker to add support for jxl where Adobe, Intel, Krita and probably others representatives said that they are insterested in the format. But this issue was closed because “no big companies are interested in jxl”.

[-] blackfire@lemmy.world 6 points 5 months ago

Isnt it Apple who was pushing jpegxl?

[-] Eiim@lemmy.blahaj.zone 9 points 5 months ago

JPEG XL has gone through waxing and waning support from each of the major browsers, but Safari is the only one to support it by default.

[-] psvrh@lemmy.ca 5 points 5 months ago

Look, I remember the early 1990s fondly, too, but I'm not eager to relive them.

[-] unreachable@lemmy.world 4 points 5 months ago

[-] apprehentice@lemmy.enchanted.social 4 points 5 months ago

I wish APNG caught on

[-] lud@lemm.ee 3 points 5 months ago* (last edited 5 months ago)

Safari is the only browser that supports Jpeg XL. Firefox does support it if you enable a flag but IIRC from bugzilla their implementation is currently not great.

If a browser feature needs to be enabled with a flag it's not really supported since an extremely tiny portion of users will be able to use it, and it's often buggy.

https://caniuse.com/jpegxl