Because they have a poor user experience with an OS and applications that have chosen not to support it properly, and blame the image format for this

I have comments about your first question, but they're mostly stupid on my end. I think the problem for most is related to your 2nd question. Google is doing it's google thing where they do a lot to force adoption with a goal of doing nothing to support it. Combine with a general distrust of Google.

I'd say the knowledge about webp's benefits is not mainstream at all, I learned about it last week from a random YouTube video. So when people download a file that isn't working as expected they don't know who to be mad at so they make memes like this.

Because it's Google trying to control not just everything ELSE about the internet, as if that wasn't enough, but even what image formats we use.

If PNG and JPEG aren't good enough, which they often are, by the way, JPEG XL is right there.

-- Frost

It's not an improvement over PNG.

but it has an optional lossless mode that no one uses

No one uses it and even if they did, you'd never know since there isn't a .webl or .webpl to differentiate lossless.

You know a PNG in lossless, you know a jpg is lossy. webp should just be assumed lossy 100% of the time.

How to determine if webp is lossless? Old format easy, jpg vs. png.

AVIF has a lossless mode. Although nobody cares for it, the slightly lossy is fine. It's adjustable just like JPEG is adjustable.

Also, it's really annoying to convert since ffmpeg can't do it yet, but the two major browsers support AV1 video, with alpha, in a .avif that you can shove into an tag. It's basically just a video. But animated. And transparent. It also works on Discord web now (but not mobile). AND you can set repetition count, if you really want. Can't show the masterpiece I've made before with that since it would be way out of topic, although here's an HD example with the animation from here:

demo

Ironically, the creators of the damn browser didn't know that it's possible and used a .webm. Well, the bourgeoisie division of the organization that makes the browser, of course. The @redhat.com emails, lol. Also, the metadata for the .webm says "ezgif". Oh welp. And yes, the greenscreen leaking at the edges was already there.

Command (bourne shell): ffmpeg -c:v libvpx-vp9 -i pop-up-1480.webm -strict -1 -f yuv4mpegpipe -pix_fmt yuva444p - | avifenc --stdin pop-up-1480.avif (-c:v needed to get ffmpeg to read the transparency).

File size:

.webm: 540KiB
.avif: 486KiB
.gif: 6.2MiB

GIF command used for comparison: gifski pop-up-1480.webm -H 832 -r 33.3333333333333333333333 -Q 100 --extra -o pop-up-1480.gif, 100% to match original quality somewhat

As someone who has edited videos and had to convert WebPs every time I accidentally downloaded them, no they do not.

Oddly enough, microsoft decided that. They are also apart of the group that owns the license to it, which includes apple and sony.

Licensing bullshit

https://www.reddit.com/r/Windows10/comments/8ptbss/comment/e0dv1d4/?context=3

https://www.zdnet.com/article/if-vlc-can-ship-a-free-dvd-player-why-cant-microsoft/

Explains it well.

Tldr: VLC is in France and doesn't have to respect copyright laws over software while Microsoft does and has to pay money for codecs per install.

You used to be able to open an heic in the native windows 11 photo viewer and go to "save as" and resave it as a jpg, but they removed it. So I guess its deliberate.

Actually I would say the the one who goes to extra health should be whoever at Apple made the decision to use the patent encumbered HEIC format as the default for iPhone photos.

There are plenty of open picture formats that do the same thing without a patent tax.

My pain isn't in the browser, it's with other apps that are still playing catch-up.

A lot of apps have added support now, but there are still edge cases. Animated webp being one. If i send that in a messaging app, usually all the other person sees is the first frame.

It's absolutely not the fault of the format, I agree, but still a cause of compatibility headaches.

It's developed by google, and google having a lead in something usually isn't a good thing. They might just make up their own extensions and stuff, and other browsers will just have to deal with this. Just like they do with other web standards.

Sometimes blorp had problems downloading .webp images, but I'm pretty sure the dev fixed it; i haven't seen those errors in a long time.

WebM works with image-rs (as long as you don't exceed your home instance's upload size limits).

I can't guarantee that every client can view it properly

that's on the client's author

but it'll show up in the Lemmy Web UI.

$ wget https://gnuplotting.org/figs/bessel.gif
$ ffmpeg -i bessel.gif bessel.webm

Try downloading that and then uploading it in a comment to to your own instance; it should work unless pawb.social limits the size.

Probably to WEBM format. And I agree with that sentiment. Much smaller file size, but you can't copy them like a gif since they're treated like a movie file.