7 ms·
Devil's argument time. They add support and there's little adoption. Worse yet, it's a meaningful amount of adoption that deprecating is now it's own criticism
by vlovich123 3y ago
Devil's argument time. They add support and there's little adoption. Worse yet, it's a meaningful amount of adoption that deprecating is now it's own criticism cycle. So now Google is being forced to add support and maintain an image format because of evangelists?
I think the problem here is that W3C is lagging on listing which image formats are standard and vendors are shipping their own in-house tech in the vaccuum (and that W3C is composed of browser vendors means Google, Apple, Microsoft, Mozila & whoever is there from the community can't agree).
- reaperducer 3y agoThey add support and there's little adoption. Who cares if there's little adoption? Why not be feature complete? It's not like Google is some cash-strapped startup. Heck, macOS ships with terminal definitions so you can log into a Mac using a Commodore B-128 as a serial terminal. It didn't have to, and that's certainly going to have less adoption than JPEG XL. (/usr/share/terminfo/62/b-128, if you're curious.) https://en.m.wikipedia.org/wiki/Commodore_CBM-II https://en.m.wikipedia.org/wiki/Commodore_CBM-II
- refulgentis 3y agoThen you fall on the sword of “google forces web standards!!” (See: WebP)
- whywhywhywhy 3y agoPhotoshop still can't open webp files, many websites still don't support uploading webp files. Do you not see how its annoying to drag a file out of Google image searches, see the extension is .jpg.webp then have to convert it back into jpeg to edit thus adding a 3rd layer of compression artifacts to the image.
- arp242 3y ago> many websites still don't support uploading webp files. On GitHub if you rename your WebP file to "file.webp.png" it will upload just fine, and will use the correct Content-Type header when serving. It's really frustrating a simple \.(png|gif|jpe?g)$ check is preventing the uploading of these files. I found this is actually the case for a number of platforms.
- bombcar 3y agoWhat's fun is when you can upload evilhacker.css.jpg and it correctly handles Content-Type as css and you exploit the tool ;)
- George83728 3y ago> Photoshop still can't open webp files, Why is Adobe so bad at their job? GIMP added webp support about 5 years ago. Paint.NET added it 4 years ago. > many websites still don't support uploading webp files. 4chan is the only such site I've heard of, and 4chan is notoriously bad at this sort of thing ever since they lost moot. It took them years to permit uploading of vp9/opus webms, for no good reason. 4chan's present administrators are incompetent, but 4chan is barely profitable (if at all) so that's not really unexpected. But Adobe rakes in huge piles of cash, so what is Adobe's excuse?
- Taywee 3y ago> It took them years to permit uploading of vp9/opus webms Did they finally do that? I left permanently a couple years ago (after being there regularly since 2006) because the small "these kinds of threads are why I still hang around this place" threads got more and more infrequent and the regular users got more and more annoying and less fun. Most of the site just became a constant pool of angry racism, cynicism, and paranoia. I can handle seeing stupid racism, but the death of fun and the constant angry sarcasm just got old. Anyway, I was constantly annoyed that I couldn't upload vp9 webms, and that apng was also not supported given how much better than gif it was. Webp would have been decent, too.
- nemo 3y agoAdobe supports WebP now: https://helpx.adobe.com/photoshop/kb/support-webp-image-format.html https://helpx.adobe.com/photoshop/kb/support-webp-image-form...
- refulgentis 3y agoHonestly have 0 idea why I’m downvoted through the floor or why you’re responding aggressively. I definitely understand it’s bad, the message I hoped was clear is it’s a bad idea to support yet another format that will take a decade to perfuse.
- arp242 3y ago> Why not be feature complete? Because this code will be exposed on every single webpage you load, and historically these kind of parsers have had a number of security problems. Something something memory safety, but this is the situation that currently exists. "All the image parsers" would be a very bad idea. Years ago there was a bug in some Linux setups where all gstreamer codecs were exposed in Firefox, and it was a huge problem (similar: https://lwn.net/Articles/708196/ https://lwn.net/Articles/708196/ – although the one I remember is much older, around 2010 or so). It's not really comparable to all the old terminfo entries from decades ago: the vendor controls those terminfo entries, not $random_websites. Maybe the ncurses terminfo parser actually does have some buffer overflow (there's an entire mini-programming language in terminfo), but if it does it's not really a huge acute problem.
- r00fus 3y agoFeatures == potential bugs. That's why. You're increasing your attack surface for critical infrastructure for many - you better be doing a cost/benefit analysis.
- reaperducer 3y agoYou're increasing your attack surface for critical infrastructure for many By that logic, Chrome shouldn't ever add any new features. WebP is also an additional attack surface.
- burnished 3y agoYeah, so features that don't have strong reasons to get implemented have a hard time being advocated for.
- Timon3 3y agoBut they didn't add support - they added support behind a feature flag. That's a massive difference.
- dpcx 3y agoDidn't they also add support for QUIC, WebP, and several others that (by nature of being internal tools at the time) had zero real world adoption?
- karaterobot 3y agoDoes anyone have an estimate on how much work it is to maintain support for JPEG XL in Chrome? Your comment sort of implies that it's the kind of thing they'd need to really weigh the pros and cons of before pushing their chips forward, but my (unfounded) assumption is that, having implemented it in the first place, the maintenance would be relatively low, essentially a dim star in the constellation of things a browser manufacturer has to maintain support for. So, it just feels odd that, faced with at least some criticism from the community, and in the face of growing support for the format (e.g. from Apple) they would choose to dig their heels in on this issue.
- izacus 3y agoIt's a C++ library that Google needs to secure and maintain security patches forever. If there's any bug in that library, it's Chrome and Google that will get blasted and blamed by rabid news media and HNers - so people here are essentially demanding that private company supports and patches their library for ever and ever. Once released, it's pretty much impossible to rollback support for media formats on the web. Behaving like there's no cost in such maintenance is just whack.
- josefx 3y ago> It's a C++ library that Google needs to secure and maintain security patches forever. Compile it to wasm and run it in a sandbox? Or throw some rust groupies at it? > Once released, it's pretty much impossible to rollback support for media formats on the web. We must live in a time where flash still dominates short web animations, streaming providers use silver light and every enterprise user is stuck waiting for the companies 5GB Java applet to load right when IE6 suddenly pops up to kill everything with an ActiveX based Windows update that adds more video codecs instead of removing them from the system. The list goes on forever. Browsers are not above killing features and breaking things for security reasons or if they just feel like it.
- magicalist 3y agoMaintaining your own rust fork of a codec or forcing the web through another painful breaking change drawn out over years seem like fantastic arguments to wait until the ecosystem is visibly moving to jpegxl before committing to it, actually.
- whywhywhywhy 3y agoWeird how none of that mattered when webp was forced on us.
- vlovich123 3y agoBecause that’s their own format and they’re willing to put in the maintenance effort. I don’t really see the equivalence. Also webp is 13 years old now or something since the initial release as compared with jpegxl which is quite new.
- worrycue 3y agoGoogle is a multi billion dollar company. They can’t spare a few developers to maintain a mostly isolated feature? (Changes and security updates to the JPEGXL will have no impact on the rest of Chrome.) If after a decade no one really uses it, fine remove it - no one will care if it’s unused. But to kill it in its cradle is just BS. JPEGXL should have the same opportunities WebP had.