JPEG-XL is better, for one, if we are talking still images, and for two, webp is just one more instance of Google forcing a preference for their own technology over others.
They refuse to implement JPEG-XL support similar to how they stripped Miracast out of Pixel devices so you can only cast to Chromecast devices unless you root your phone and put on LineageOS, which has brought back Miracast.
Things like webp are Google trying to do an end-run around web standards with the intent of allowing Google, the company, to be the final arbiter of web standards instead of the W3C (World Wide Web Consortium).
People who hate webp are most likely people who hate Google’s quest to dominate the web and be the arbiter of standards.
Ah well that’s certainly fair enough, I had no idea it’s a Google-encumbered format.
Not sure I’ve ever “voluntarily” converted something to webp. Many Lemmy instances’ pict-rs setups seem to use it, my home instance sopuli.xyz obviously being one of them, which I guess is a sort of a funny choice considering
In September 2023, two critical vulnerabilities[108] relating to WebP images were discovered by Apple Security Engineering and Architecture (SEAR) and the Citizen Lab, potentially affecting Google Chrome, Chromium-based browsers and the Google’s libwebp project, among any application implementing libwebp. Among these vulnerabilities, CVE-2023-4863 was an actively exploited vulnerability with a high risk rating of CVSS 8.8. This could lead to an out of bounds/overflow condition in applications using the affected libwebp library, upon exploitation of a maliciously crafted .webp lossless file. This could result in a denial of service (DoS), or worse, enabling malicious remote code execution (RCE). The extensive use of libwebp packages across hundreds of applications, including all categories from web browsers to mobile apps, posed a major patching challenge to mitigate the vulnerability due to the demanding testing requirements before release, highlighting the implications of this vulnerability on a wide scale.
JPEG-XL is better, for one, if we are talking still images, and for two, webp is just one more instance of Google forcing a preference for their own technology over others.
They refuse to implement JPEG-XL support similar to how they stripped Miracast out of Pixel devices so you can only cast to Chromecast devices unless you root your phone and put on LineageOS, which has brought back Miracast.
Things like webp are Google trying to do an end-run around web standards with the intent of allowing Google, the company, to be the final arbiter of web standards instead of the W3C (World Wide Web Consortium).
People who hate webp are most likely people who hate Google’s quest to dominate the web and be the arbiter of standards.
Ah well that’s certainly fair enough, I had no idea it’s a Google-encumbered format.
Not sure I’ve ever “voluntarily” converted something to webp. Many Lemmy instances’ pict-rs setups seem to use it, my home instance sopuli.xyz obviously being one of them, which I guess is a sort of a funny choice considering
I wasn’t even aware of it being a format from google. My personal issue is that some programs and apps I use don’t support webp
Citation needed
https://en.m.wikipedia.org/w/index.php?title=WebP
So what, we’re not supposed to use any library that’s ever had a vulnerability? You better go uninstall literally everything on your computer then
It is a modern successor to formats like WebP & JPEG. WebP was barely competitive with JPEG
Citation needed
https://giannirosato.com/blog/post/image-comparison/