5 ms·
They'll do literally anything rather than implementing JPEG XL over AVIF in Chrome, huh? I mean, of course this is still valuable (JPEG-only consumers will pro
by lxgr 3y ago
They'll do literally anything rather than implementing JPEG XL over AVIF in Chrome, huh?
I mean, of course this is still valuable (JPEG-only consumers will probably be around for decades, just like MP3-only players), and I realize Google is a large company, but man, the optics on this...
- whywhywhywhy 3y agoIf you do creative work countless tools just don’t support webp, AVIF or HEIF. It’s so prominent running into files you can’t open in your tools that I have a right click convert to PNG context menu
- jiggawatts 3y agoThey don’t support it because Chromium doesn’t. Because Chromium doesn’t support it, Electron doesn’t. Because Electron doesn’t, Teams and other modern web apps and web sites don’t either, etc… If Google just added JPEG XL support instead then it would be… a supported alternative to JPEG. You’re saying working in that is a waste of time because… it’s not supported.
- n2d4 3y agoChromium does support WebP and AVIF, yet parent's tools don't.
- The_Colonel 3y agoMaybe because WebP and AVIF are actually not that great image formats. WebP has been critiqued as a very mediocre improvement over JPEG all the way since its introduction. These formats are in Chromium because of Google politics, not because of their technical merit.
- deleted 3y ago[deleted]
- modeless 3y agoThere's a lot more to format support than Chromium. There's a pretty strong meme out there on the Internet that webp is evil despite being supported in all browsers for years because there's still a lot of software out there that never added support and people get annoyed when an image fails to open.
- redeeman 3y agomaybe proprietary software just isnt so good?
- deleted 3y ago[deleted]
- lxgr 3y agoI don't think it's evil, but I just don't think it's very good either. And a graphics format better be damn good (i.e. much, not just a little bit, better than what it's hoping to replace) if it aspires to become widely supported across applications, operating systems, libraries etc.
- account42 3y agoFormat quality has fuck all to do with widespread support. Widespread support comes from either widespread use (forcing companies to implement support) or from enabling new things.
- jug 3y agoAt least now with Jpegli, this will surely be the nail in the coffin for WebP? The article has 35% compression improvements over JPEG mentioned and that's at least as much as usually thrown around when discussing WebP.
- account42 3y agoAnd let's not forget that the advantages of WebP are already often way overstated compared to how things really match up when you don't just really on shitty metrics to pretend that images have the same quality.
- whywhywhywhy 3y agoTalking about things that don’t pass through webtech photoshop, after effects, illustrator, Final Cut, davinchi, 3d software, rendering engines etc
- account42 3y agoNot a fan of any of these video keyframe base image formats but if your tools don't support them by now then you really should get better tools.
- refulgentis 3y agoI have no love for Google, at all. It's really hard to say this in public, because people are treating it like a divisive "us or them" issue that's obvious, but the JPEG-XL stuff is _weird_. I've been in codecs for 15 years, and have never seen as unconstructive behavior like the JPEG-XL work. If I had infinite time and money and it came across my plate, we'd have a year or two of constructive work to do, so we didn't just rush something in with obvious issues and opportunities. It turned into "just figure out how to merge it in, and if you don't like it, that's malfeasance!" Bread and circus for commentators, maybe, but, actively preventing even foundational elements of a successful effort.
- lxgr 3y agoTo be honest, at Google scale, if there's an objectively good new codec with some early signs of excitement and plausible industry traction, and even Apple managed to deploy it to virtually all of their devices (and Apple isn't exactly known as an "open codec forward" company), not integrating it does seem like either malfeasance or gross organizational dysfunction to me.
- refulgentis 3y agoCompletely hypothetical scenario: what if the technical reaction was so hostile they invested in it themselves to fix the issues and make it sustainable? In light of the recent security incident, I'd see that completely hypothetical situation as more admirable.
- lxgr 3y agoHm, are you suggesting they're currently in the process of reimplementing it in a safer and/or more maintainable way as part of Chrome? In that case, that would just be extremely bad messaging (which I also wouldn't put past Google). Why agitate half of the people on here and in other tech-affine parts of the Internet when they could have just publicly stated that they're working on it and to please have some patience? Public support by Google, even if it's just in the form of a vague "intent to implement", would be so important for a nascent JPEG successor.
- ur-whale 3y ago> They'll do literally anything rather than implementing JPEG XL over AVIF in Chrome, huh? Before making that kind of claim, I would spend some time looking at the names of the folks who contributed heavily to the development of JPEG XL and the names of the folks who wrote jpegli.
- lxgr 3y agoBy "they" I mean "Google, the organization", not "the authors of this work", who most likely have zero say in decisions concerning Chrome.
- JyrkiAlakuijala 3y agoChrome advised and inspired this work in their position about JPEG XL. Here: https://www.mail-archive.com/blink-dev@chromium.org/msg04351.html https://www.mail-archive.com/blink-dev@chromium.org/msg04351... "can we optimize existing formats to meet any new use-cases, rather than adding support for an additional format" It's a yes! Of course full JPEG XL is quite a bit better still, but this helps old compatible JPEG to support HDR without 8-bit banding artefacts or gainmaps, gives a higher bit depth for other uses where more precision is valuable, and quite a bit better compression, too.
- IshKebab 3y agoDespite the answer being yes, IMO it's pretty clear that the question is disingenuous, otherwise why did they add support for WebP and AVIF? The question applies equally to them.
- lxgr 3y ago> "can we optimize existing formats to meet any new use-cases, rather than adding support for an additional format" Only within pretty narrow limits. Classic JPEG will never be as efficient given its age, in the same way that LAME is doing incredible things for MP3 quality, but any mediocre AAC encoder still blows it out of the water. This is in addition to the things you've already mentioned (HDR) and other new features (support for lossless coding). And I'd find their sentiment much easier to believe if Google/Chrome weren't hell-bent on making WebP (or more recently AVIF) a thing themselves! That's two formats essentially nobody outside of Google has ever asked for, yet they're part of Chrome and Android.
- dchest 3y agoSome authors of this are also the authors of JPEG XL.
- lxgr 3y agoI saw that. It's the tragedy of Google in a nutshell: Great things are being worked on in some departments, but organizational dysfunction virtually ensures that the majority of them will not end up in users' hands (or at least not for long).
- ksec 3y agoThis is work from Google research outside US. You could even call it a different company with the same name. It is Google US who made those AOM / AVIF decisions.
- out_of_protocol 3y agoWhy no blame on Mozilla for ignoring format as well?
- simon_o 3y agoMozilla only does what Google tells them.
- out_of_protocol 3y agoWhy bother promoting firefox then? If they have no will of their own, you're screwed anyway. Might use chrome as well