431
jprule
(lemmy.blahaj.zone)
webp feels like a cancer
The original quote
The fact that Kissinger outlived Bourdain proves there is no God.
Though I almost wish Kissinger had lived long enough to see Trump piss away the American power and influence Kissinger sold his soul for. Kissinger should have lay on his deathbed knowing his successors squandered every advantage he won for America, that he steeped his hands in blood and made himself the greatest war criminal in history for nothing.
For people like that I can’t even imagine that they don’t do it for the love of the game. Things always go better for everyone when we work together(should still tell nazis to sit on a stick and rotate, though), people in positions of power like that are cruel for cruelty’s sake. All he did was create more enemies for his country and chased more hate like the lady who swallowed a fly. It never got better because all he did was inject poison into the world and didn’t use any of the US’s influence or power to actually help anyone.
Just a huge piece of shit all around.
tom lehrer outlived kissinger at least!
More compelling than the edit, thank you for posting this.
https://www.bbc.co.uk/news/world-asia-67582813
^ an article describing some of the reason Kissinger was such a vile person, including how he shares some of the responsibility for the rise of the Khmer Rouge
Google has apparently been mogged into rewriting the jpegxl reference library in rust to make it more “secure” so that it can be used in browsers (apparently the reason they refuse to put it in chrome, and the reason firefox devs cite) (never mind the fact that this apparently didn’t stop Apple) we can only hope they actually finish the damn thing…
To be fair, this isn't just happening out of the blue. Apple had a bunch of zero day, no click vulnerabilities from its media decoders, which were some of the original Pegasus vectors. Complex media rendering is a very legitimate security concern, particularly in the browser space on general purpose machines. IDK if doing a full RUST implementation is the right answer, but the idea of not wanting to add a massive potential attack vector for redundant functionality is not completely insane.
I uploaded a meme in .jxl and everyone downvoted it because they couldn't see it. If you use a firefox fork please enable it ffs.
Is it not enabled by default in firefox?
Firefox only packaged it in nightly builds.
Stable has the setting but it does nothing.
Nope, Mozilla doesn't trust it to be secure. A newer Rust decoder for Firefox is in development.
The setting is image.jxl.enabled for those who want to try it.
can you even enable it as an option? I thought they removed it because of "attack surface" concerns
In can be enabled in about:config but only in nightly. It works in most forks as well. A Rust decoder for .jxl is in development. Mozilla said they will include it in Firefox when finished
~~i just enabled it in firefox stable, 143.0, linux ~~
edit: i have been bamboozled, it does nothing
test your browser for jxl support: https://jpegxl.info/resources/jpeg-xl-test-page
Did it actually work?
check if it actually works, last time it didn't do anything for me
ah yeah, is that rust implementation the one being written by the chromium jxl team?
For f*&% sake, I'm using JPEG XL on my website for some high res images that are amazingly well compressed using it, and especially to reduce the repository size on Codeberg. Only now discovered that only my niche main browser, Zen, renders them. What a stupid decision; their compression of high quality images is superior. Perfect to use alongside AVIF which does better in low quality images and illustrations and the like, or PNG which is best at preserving images containing text such as screenshots.
Safari renders them.
Firefox forks usually render them because Firefox supports it but Mozilla takes it out of packaged builds.
load more comments
(3 replies)
Current Android news have me wanting to beat Google to death
This might be an unpopular opinion, but webp fulfills the same use cases and some more. But it's not jpeg and some SW still doesn't support it.
Except webp has worse compression, doesn't support HDR and has a max colour depth of 8bpc. What makes JPEG-XL great is that it covers loads of use cases and is very future proof.
Webp, on the other hand is "current-proof". JXL's biggest issue is getting adoption, not the technical aspects.
The meme is right, chrome/ium support would do a lot to help adoption. But not even the mainline FF version has support (AFAIK).
edit: the option doesn't seem to actually enable support
stable firefox has an option to support it, in about:config that is set to false by default
Webp is "current-useless" on account of being unsupported by a lot of software, including Google's own office suite. Just the same as jxl.
At the end of the day, any standard or protocol that is not widely supported is de-facto useless. Some examples are: ipv4 multicast, TCP multipath, MIR, hashcash; all of this are technically valid, but nothing supports them, so it doesn't matter
Except .jxl is backwards compatible with .jpg. You can losslessly convert a .jpg to a smaller .jxl file. Also .jxl is future proof and supports ridiculously high resolutions up to 1 terapixel.
JXL is better on paper/technical specs, but adoption is terrible while wepb is already here as it replaced gifs and most web images.
I have nothing specific against JXL, it's a good format, but I don't feel its necessary either.
Yeah, I guess if we're being pragmatic/reasonable, you are right. I think jxl use and general adoption would be much more of a symbolic win than a technical one. The problem is that a new image format only reaches general adoption if Google supports it. Webp is a decent Google-developed standard that has reached general adoption because Google pushed and supported it and if Google doesn't support jxl, then you can't use it on the general internet.
This is not about jxl being the better standard, this is about the better standard being non-viable because Google doesn't want it to be.
The caveat here is that jxl is not half as old as webp and this situation might change drastically in a matter of months (I bet ff would be quick to adopt jxl if Google did...) ((although the jxl standard is technically 3 years older than the webp standard))
Webp adoption also used to terrible, but now it's mostly fine.
Kinda missing the point here.
One company shouldn’t be able to pick winners and losers for file formats or protocols.
Google has done it over and over again: https://en.wikipedia.org/wiki/QUIC
Pretty sweet gig, being able to give yourself an 8-year head-start.
They released the gQUIC reference implementation under the BSD-3 licence. What would have been your preferred way?
Google is a monopoly, consequently most of their in-house tech will make waves if they decide to use it.
Or are you suggesting a nefarious purpose, like MS's EEE?
There’s not really a better way when you’re a monopoly. That’s the problem.
With QUIC and with webp, there was no period of time where the new protocol/format had to compete against other experimental options to see which would win out.
Because Google put it out, and they control an overwhelming share of clients and servers, they were both a foregone conclusion. Google released it, so now it’s a standard. Other companies can either adopt it or fall behind.
This allows them to stack the deck in favor of their portfolio, even if other options were technically superior.
I mean the alternative is what Microsoft does with xml documents where they participate in the standards committee, release a reference implementation, and then intentionally break it in Office so idiots whine about open tools "not rendering correctly"
Fuck webp and the horses it rode in on.
Or I should say, the several supported horses it rode in on, and the rest of the horses standing there looking confused like they have no idea what a webp is even though they can make a preview thumbnail of the webp image, but just can't do anything else with it.
Why is this topic so hot right now? What did I miss?
i just saw a post hating on webp on my timeline, and happened to have recently talked with a friend about image formats, wherein this image was made. so i just kinda thought it would be relevant to post
It’s been hot since webp was introduced.
Jxl is just the best image format at present.
view more: next ›
this post was submitted on 22 Sep 2025
431 points (98.2% liked)
196
18411 readers
283 users here now
Be sure to follow the rule before you head out.
Rule: You must post before you leave.
Other rules
Behavior rules:
- No bigotry (transphobia, racism, etc…)
- No genocide denial
- No support for authoritarian behaviour (incl. Tankies)
- No namecalling
- Accounts from lemmygrad.ml, threads.net, or hexbear.net are held to higher standards
- Other things seen as cleary bad
Posting rules:
- No AI generated content (DALL-E etc…)
- No advertisements
- No gore / violence
- Mutual aid posts are not allowed
NSFW: NSFW content is permitted but it must be tagged and have content warnings. Anything that doesn't adhere to this will be removed. Content warnings should be added like: [penis], [explicit description of sex]. Non-sexualized breasts of any gender are not considered inappropriate and therefore do not need to be blurred/tagged.
If you have any questions, feel free to contact us on our matrix channel or email.
Other 196's:
founded 2 years ago
MODERATORS