WEBP is a cancer

I'm going to blow your fucking mind;

Right Click
Copy Image
Open MSPaint
Paste Image
when the output file has garbage.

you'll learn eventually.

Also what I'm describing isn't a conspiracy when you can rattle off websites that won't let you use the copy function at all and you have to snip an image. Sure sometimes you might be able to pull the images direct link from the sites source but that's not 100% either. This didn't start last year this has been going on for well over a decade in regards to content control.

I think it was Genius lyrics that started the trend when you tried to print their lyrics directly without first copying it to a notepad to clean it up it injects the sites URL into the text field multiple times. And then for a period they disabled copying stuff from their site directly at all. you're just comfy with forums and have forgotten how bad the internet had gotten prior to a silly Google owned Image format. it does save space though.
 
There are ways to convert WEBP images to JPEG, but it's annoying as fuck, not based at all. And every year image search in all browsers gets more and more clogged. Wish the format would die.
 
1728053575472.png
It also doesn't help that the guy who made WEBP spends all day on twitter defending his shitty format, instead of, ianno, FUCKING CODING IT TO WORK WITH MORE SHIT.
 
It also doesn't help that the guy who made WEBP spends all day on twitter defending his shitty format, instead of, ianno, FUCKING CODING IT TO WORK WITH MORE SHIT.
That's not the problem, 95% of software that's been updated in the past 5 years but doesn't support webp is likely simply laziness. The libraries they use to process images almost certainly support webp already, and if not, there are tonnes of tools out there to encode and decode them. He can't really do anything about it.
 
  • Like
Reactions: Gog & Magog
That's not the problem, 95% of software that's been updated in the past 5 years but doesn't support webp is likely simply laziness. The libraries they use to process images almost certainly support webp already, and if not, there are tonnes of tools out there to encode and decode them. He can't really do anything about it.
Google nigger detected.
 
Lol please do share how his completed encoding and decoding libraries getting more bloated would make more software support it.
It's only being pushed because a company currently under an anti trust suit is pushing it and stifling a better format, that being JPEGXL. The software is shit, and no one wants this pajeetware being crammed down our throats.

WEBP solved nothing, because there was nothing to solve, instead, WEBP did the reverse and created a problem that Google wants us to solve.
 
It's only being pushed because a company currently under an anti trust suit is pushing it and stifling a better format, that being JPEGXL. The software is shit, and no one wants this pajeetware being crammed down our throats.
Literally nothing to do with what I said lol. You said he spends too much time tweeting, not developing. I said the development is over on his side and it's up to other programs to implement his format and his code he's put out into the world. Then you decided to go on a Google rant.
 
  • Like
Reactions: Gog & Magog
Literally nothing to do with what I said lol. You said he spends too much time tweeting, not developing. I said the development is over on his side and it's up to other programs to implement his format and his code he's put out into the world. Then you decided to go on a Google rant.
My point still stands, no one want want to support this shit ass software because it didn't solve any problems. There's clearly still a problem that he's opt not to solve if no one wants it.
 
My point still stands, no one want want to support this shit ass software because it didn't solve any problems.
Its not supported cos Google, Apple and Microsoft all want to slap their dicks about and hinder each others progress. The point was to reduce file size, which it does. Bandwidth usage is a huge problem.

Webp isn't particularly amazing, but nobody would give two shots about it outside developers if their OS, browser and image editor can open it. Do you really have any technical issues with it? It's just one comoressed format in a sea of others. What don't you like about it, other than software other people make don't support it?

And before you google rant me again, my first reply opened with it being Google owned is the main issue.
 
Webp isn't particularly amazing, but nobody would give two shots about it outside developers if their OS, browser and image editor can open it. Do you really have any technical issues with it? It's just one comoressed format in a sea of others. What don't you like about it, other than software other people make don't support it?
If you want me to pin down an issue, it's that when I try to discuss fandom things, I need up rushing to sources that don't use JPEG or PNG, but WEBP, and I end up posting things into places where it doesn't format right. Take telegram for example, when you post a WEBP, it treats it as a sticker, and not an image, because Telegram can't differentiate from the two.

If you want an actual problem I have with it, it's that I wish sources for fandom related content did not use WEBP, or gave me an option to obtain things in JPEG or PNG.
 
If you want me to pin down an issue, it's that when I try to discuss fandom things, I need up rushing to sources that don't use JPEG or PNG, but WEBP, and I end up posting things into places where it doesn't format right. Take telegram for example, when you post a WEBP, it treats it as a sticker, and not an image, because Telegram can't differentiate from the two.

If you want an actual problem I have with it, it's that I wish sources for fandom related content did not use WEBP, or gave me an option to obtain things in JPEG or PNG.
Which are the problems I already proposed before you first replied. The bit of your post I replied to is

It also doesn't help that the guy who made WEBP spends all day on twitter defending his shitty format, instead of, ianno, FUCKING CODING IT TO WORK WITH MORE SHIT.

Which isn't how software development works.

We could have had the same format wars when we went from BMP to JPG and GIF, or GIF to PNG and all the thousands of other small formats and containers, and if software didn't support them, you could make many of the same arguments you could make against webp. It doesn't make it a bad format or bad software. It's just an example of big tech shooting both us and themselves in the foot in pursuit of not being seen to use each others software.
 
  • Like
Reactions: Gog & Magog
We could have had the same format wars when we went from BMP to JPG and GIF, or GIF to PNG and all the thousands of other small formats and containers, and if software didn't support them, you could make many of the same arguments you could make against webp. It doesn't make it a bad format or bad software. It's just an example of big tech shooting both us and themselves in the foot in pursuit of not being seen to use each others software.
Then why not just kill the damn thing? Google is usually pretty good at taking things out back with a shotgun.
 
Then why not just kill the damn thing? Google is usually pretty good at taking things out back with a shotgun.
They're trying to with AVIF, which has the added benefit of basically being a still frame of their video encoding tech, which means less duplicated resources. However there are other competitors, like JPEGXL, which Apple has always supported (and Google has variously supported and deprecated over the years). They are trying to supplant it. There's just more slapfights going on
 
Back