Why are we sending someone to “Extra Hell” for making an improved image format that has better compression and is an overall improvement over all 3 of the existing formats it replaces (jpeg, png, gif)?
Shouldn’t this apply to everyone the companies who refused to adopt it, thus breaking every normal image workflow? (Same thing can be said about JXL)
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’m realizing my wording might be vague, by “everyone” I meant the big tech companies that didn’t implement it, like Google, Apple, Microsoft, and Adobe. AFAIK most of the open source apps actually implemented support pretty quickly, and obviously it wouldn’t be the end users’ fault because they can’t change what formats are supported
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.
Obviously be mad at whoever responded to a request without accept webp in it with a webp or didn’t provide an alternative. Nothing wrong with supporting webp with a fallback
Why are we sending someone to “Extra Hell” for making an improved image format that has better compression and is an overall improvement over all 3 of the existing formats it replaces (jpeg, png, gif)?
Shouldn’t this apply to
everyonethe companies who refused to adopt it, thus breaking every normal image workflow? (Same thing can be said about JXL)Edit: fix vague wording
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’m realizing my wording might be vague, by “everyone” I meant the big tech companies that didn’t implement it, like Google, Apple, Microsoft, and Adobe. AFAIK most of the open source apps actually implemented support pretty quickly, and obviously it wouldn’t be the end users’ fault because they can’t change what formats are supported
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.
Obviously be mad at whoever responded to a request without accept webp in it with a webp or didn’t provide an alternative. Nothing wrong with supporting webp with a fallback
It’s not an improvement over PNG.
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.