I do hope other browser makers like Mozilla Firefox and Apple Safari will hold back on this, like they should have done with Webp v1.
(Disclosure: I work for Google, speaking only for myself)
Mozilla always had the stance that they wouldn't just add support for technology that might be just a passer-by technology. I think that was the right choice and I think it is a shame they added support for webp recently.
I can even imagine this to be market practice, where they add new stuff, where Apple and Mozilla and newcomers have to chase Google's fad of the day, while Google has enormous resources for Chrome. You can call me paranoid, I probably am :)
Anyway, if Google Chrome ditches Webp v1 in the next 10 years, I will not be that guy to say "Told you so!", but I will think it for sure.
The browser cannot drop support for an image format without major compatibility issues.
If you would like to bet on whether webp is still supported in Chrome in a decade I'd be happy to ;)
(Disclosure: I work for Google, and have no internal information on this)
This is a strawman, at no point am I or would I ever claim this is a good idea.
At what point is progress too much progress? Why can't we also balance these things with backwards compatibility, interoperability, accessibility, and other such things?
> least technically inclined
How many people actually know what WebP is, as opposed to thinking its some sort of bug with google or their browser? The least technically minded are more than a majority of users, more like the vast majority. Is their usage not valued?
It seems odd that Google is being punished for releasing their work to anyone who wants it.
"We made this thing because it solves a problem we have, and we're giving it away so it might solve the same problem for you" doesn't seem nefarious.
If nothing else, just provide a slow-but-correct decoder that translates the format to a long term stable format (e.g. PNG).