- cross-posted to:
- programmerhumor@lemmy.ml
- cross-posted to:
- programmerhumor@lemmy.ml
You must log in or register to comment.
Webp’s purpose is to display images on web pages in a format that allows fast loading and rendering. When a user downloads or views an image it should be served in a better format. Webp serves it’s purpose perfectly. Don’t try to download a background of a webpage with the expectation that it will be in a format that is not beneficial to the pages function.
WebP has all the functionality of jpg, png, and gif while still being a smaller filesize. It has baseline support across browsers and devices. I’m no Google simp and work to de-google my family and workplace but this is a hill I will die on. Webp currently the best image file format.
It is. The sentiment comes from majority of Americans using Apple operating systems, which refused to support WebP until recently.
At this point I think Facebook messenger and internet explorer are the only ones that don’t support it. Oh and maybe the ISS.
Somewhat related: Does anyone know why so many of the images uploaded to Lemmy are GIFs? Or at least download in that format when using Sync? It’s kind of annoying because they aren’t animated, they are completely static images, and all that does is cause problems with sending them in other apps. I frequently have to download an image, take a screenshot of it, and crop it to the original size again.
so sad to see so many google simps blinding defending this crap
I actually use it for creating thumbnails for a sorta niche application. The resulting files are quite small and the quality is fine. I do remember it being a pain in the ass to deal with ~10 years ago.
The first part is wrong. And the second part is mostly wrong. Stop whining
Pro tip: If discord is complaing your screenshots are too large convert them to avif or webp. Now you don’t need nitro
I have never had a screenshot exceeding 40 MB. That is humongous.
If you screenshot computer/phone interfaces (text, buttons, lots of flat colors with adjacent pixels the exact same color), the default PNG algorithm does a great job of keeping the file size small. If you screenshot a photograph, though, the PNG algorithm makes the file size huge, because it’s just really poorly optimized for re-encoding images that are already JPG.
What if I want to screenshot my cocaine-fueled rant to my ex and mistakenly send it to said ex instead of my homies?
Webp has both a lossy and lossless mode so the first part of this meme is lost on me
I guess that was the lossy part :)
| | | | | | _
Never understood why jepgXL didn’t win out
It’s slowly marching along with the reimplementation of its reference decoder in rust. That should hopefully satisfy google and mozilla’s demands and get them to adopt it in their browsers.
Because Google didn’t invent it, and Google decides what does and doesn’t get added to the Internet.
Google were literally one of the three organisations who worked on the standard, and the top contributor to the reference implementation works there.
It’s different people who develop and who decide.
And then they killed it. It was Google pulling support in Chrome that killed JPEG-XL’s momentum.
It was the Joint Picture Experts Group that invented it, so Google had no ownership over it, unlike WebP.
Google’s stance on JPEG XL is ambiguous, as it has contributed to the format but refrained from shipping an implementation of it in its browser. Support in Chromium and Chromeweb browsers was introduced for testing April 1, 2021[29] and removed on December 9, 2022 – with support removed in version 110.[30][31]The Chrome team cited a lack of interest from the ecosystem, insufficient improvements, and a wish to focus on improving existing formats as reasons for removing JPEG XL support.[29][32][30]
The compression technique it used was patented, and the licence fee was extortionate. By the time the patent expired, other, royalty-free, techniques were available that outperformed it.You’re thinking of jpeg2000
Oops. I’d somehow missed that there was now a third kind of JPEG.
Yes, I would like to waste 500 KB over the wire for an image of indistinguishable quality
I hate that Messenger doesn’t support webp. Makes sharing from Lemmy quite annoying. Signal takes webp though, no prob.
I screen shot and crop every meme i want to share from Lemmy. It is tedious.
I have a better solution that I found out by accident.
So you initiate the sharing, right, then before you select the Messenger app (or whichever app that doesn’t handle webp), you click the little edit button on the image above the shareable apps. That brings up cropping and other adjustments. But from here, you can just hit the big Share button immediately to share the image practically losslessly (without cropping mistakes and such). It brings up the share thing again but this time the image will be in a shareable format, presumably PNG(?).
Spread the word!
(This is on Android btw.)
Quality loss? Webp supports lossless.
So does JPEG. It doesn’t mean that people (will) use it for that.
Actually? I didnt know that. Is it used often? Any downsides ?
Practically never because it’s rubbish. The only possible use is on old precision machines that don’t support newer standards, like medical imaging.
I really don’t get the WebP hate, it’s a good format. It’s better than PNG and JPG.
Though you couldn’t set the bar any lower without it turning into a joke.
Anyhow, to quote Wikipedia:
Comparing different encodings (JPEG, x264, and WebP) of a reference image, she stated that the quality of the WebP-encoded result was the worst of the three, mostly because of blurriness on the image. […] In October 2013, Josh Aas from Mozilla Research published a comprehensive study of current lossy encoding techniques and was not able to conclude that WebP outperformed JPEG by any significant margin
All while having significantly increased complexity. The blurriness problem was inherited from the video codec webp was based on. When you can’t beat an 18 years old format, don’t be surprised when people get irritated when you use your position to get it mandated into a standard, while later stalling actual improvements (JPEG XL).
Is JXL in actual use? Is it supported? I reckon it’s quite new, innit? D’you happen to.know how it compares to its peers?
It’s not supported by either Chromium or Firefox, which is part of the issue (Google basically decided against it with arguments that are much better suited against WebP, which they pushed some years ago).
There aren’t that many static image codec comparisons, for example there is https://giannirosato.com/blog/post/image-comparison/. https://afontenot.github.io/image-formats-comparison/ doesn’t even include WebP because the test suite uses features unsupported by it (YUV 4:4:4). In the ones I do find, WebP usually wins against good JPEG at low bitrates, but loses on high bitrates because of the blurriness issue. They both get beaten by JPEG XL and AVIF. Which one is better probably depends on whom you ask. The before linked comparison prefers JPEG XL by a slim margin, https://tonisagrista.com/blog/2023/jpegxl-vs-avif/ strongly favors JPEG XL.
JPEG-XL exists, is factually better, and is not patent encumbered.
How is WebP “patent encumbered”? It’s an open format.
Open is not the same as patent-free, the two things can coexist (and they do in the case of webp).
It’s open to write the code, but in order to be authorized to use it you have to get a permit from Google. You can’t eg.: fork from Firefox and use their permit (as you implicitly could with patent-free). Plus, Google can rescind their patent grant at any point, which they are bound to do once they secure ownership of the internet.
That’s just not true.
Thanks for taking the time to disprove this
does jpeg xl support animated images?
It does, yes, but from what I gather it’s rather difficult to actually encode such an animated image compared to, say, a GIF. Display should work just fine.
Yes, but that is actually almost “incompatible with every app and website”
A file format can not, by itself, be “incompatible” with a website. What matters is the browser, and Firefox at least is adding support (slowly), and they are the ones who matter ATM.
PNG is lossless, so isn’t that like comparing apples to oranges?
Edit: Apparently webp can also be lossless. I don’t know anything.
It’s just tech illiterate being “oh no my image program not open this 10 year old new format”
This meme is out of date.
What - doesn’t - support webp at this point? P much all maintained open source software has for years upon years, os x has for years, Android and iOS have for ages as well, even windows added support a year ago or so supposedly.
Like are these memes made by confused time travelers?
even windows added support a year ago or so supposedly
You answered your own question. I spent years playing the game of “This image is a JPEG. Will the website force me to save it in a format that can’t be opened by the basic Windows photo viewer, or will it actually be a JPEG when I download it?”
You’d be surprised how often it would turn out to be the former rather than the latter.
Windows photo viewer sucks, that’s your problem
Nomacs is a better alternative. Not perfect, but FOSS and faster than windows https://nomacs.org/
It’s often a nightmare when sharing to chat apps to show friends memes etc
a) send links instead of polluting my storage with garbage, please
b) use Signal, it does webpFor the first point, I’m just going to throw out that sending the content can be preferable given how likely the link is to go dead eventually. There are a number of things I can no longer find because of this although it is admittedly an edge case.
Well yeah, but for memes, longevity isn’t really a priority.
It somewhat is for me, my partner takes days or weeks to click my links.
Sounds rough
Nah it’s pretty normal. You’re not always in the mood, maybe you receive a lot of content from other people as well
Well, yeah, but for memes longevity isn’t really a priority imo.
Discord doesn’t and a lot of other apps neither
Discord supports webp. I use it regularly.
Then is it Samsung’s flavor of android that is to blame ?
I’ve never had an issue with webp on Samsung devices, either in Discord or not.
Might be, that one I can’t test, I don’t have any samsung devices.
