3 ms·
It's hard to be anything but skeptical about the intent behind this decision, considering that the competing emerging standard (WebP) is one that Google control
by least 4y ago
It's hard to be anything but skeptical about the intent behind this decision, considering that the competing emerging standard (WebP) is one that Google controls.
This is one reason why I am thankful that Apple still only allows webkit on iOS even if philosophically I believe people should be able to run the software they want on their phone — it's basically the only check against pure Google hegemony over the web.
> can we optimize existing formats to meet any new use-cases, rather than adding support for an additional format; do other browsers and OSes support it?
They did not show this restraint at all when it came to implementing and pushing their own formats.
- jsnell 4y agoThis is a really strange take, because Apple does not support JPEG XL and was never going to support it. And since nobody else can bring that support to iOS either, the format as a whole is dead to the web. (And, uh, I don't know where you're getting webp from here. The competition for this generation of image formats is AVIF; AVIF has been blessed by Apple, so no matter how distasteful it is that's what we'll get.) > They did not show this restraint at all when it came to implementing and pushing their own formats. JPEG XL was largely a Google-created format.
- jonsneyers 4y agoThe Chrome team did not create JPEG XL, that was a totally different team. The Chrome team did create WebP and was heavily involved in the creation of AVIF.