Comment on Chrome, Firefox and other browsers affected by critical WebP vulnerability
thedirtyknapkin@lemmy.world 1 year agoone important tidbit in this whole situation that sheds a lot of light on where and why is adopted: webp is Google’s horse, jpegxl is adobe’s horse. that’s why jpegxl has poor web support, and why webp pisses off designers.
Lucidlethargy@sh.itjust.works 1 year ago
It doesn’t piss off designers, but we’re pissed at Adobe for making us search for and download plugins to support it.
Seriously, fuck Adobe.
thedirtyknapkin@lemmy.world 1 year ago
eh, it’s just two stubborn corporate entities trying to throw their weight around. the only reason adobe looks bad here is because Google is winning. they both stubbornly refuse to allow the other’s standard on their platforms.
jpegxl is the better format, without a doubt, but adobe is a fool if they think they can strongarm Google.
to me, adobe is being foolish, but they’re both equally being evil.
Lucidlethargy@sh.itjust.works 1 year ago
Google doesn’t really compete in the professional space, though. Adobe does, and we need these tools for a huge number of reasons. When I first started seeing webp’s, I kept trying to use them in projects and was unable. I was passing them through online converters for a little bit before realizing there was a plugin.
I don’t care which one wins, or which one is more heavily adopted… I just want to see ALL of those in my tools I need for my job.