Thread 106996328

When will Hiro start supporting this technology?

hopefully never

shit technology, spit on webp and all of it's advocates!

>>106996328 (OP)
When rapeape stop having a skill issue, never.

>>106996328 (OP)
It’s not a technology, it’s another google scam.

>>106996328 (OP)
Never because 90% of 4channers have 0 fucking clue that it replaces GIF and PNG better than it replaces JPG. So all they see is a JPG converted to webp and will go around moaning "WEBP BAD!".

BEST case scenario is we get jpeg2000 and I'm not joking. We recently got H264 support instead of AV1. 4chan is officially the fax machine of the internet.

no usecase

web penis

>>106996454
:----------DDd

when are we getting AV1 and HEVC
when are we getting JPEG XL
when are we getting AVIF
when are we getting gifv
when are we getting literally anything good

>>106996547
You VILL get JP2000
UND
YOU VILL BE HAPPY

What's up with that? At least do it for the thumbnails. Would save a lot of bandwidth.

>>106996357
It's more efficient than jpeg. Even lossless webp is far better than png. You wouldn't use bmp instead of png in 2010.

>>106997505
There's some nuance there. Webp IS more efficient than a very specific variant of JPEG that uses chroma sub sampling.

There's 3 versions of JPG:
420 blaze it JPG
422 muh 1337 photography JPG
444 muh fidelity JPG

Other than that yeah, Webp curbstomps PNG/GIF 6 feet under the ground.

What is the usecase for webp?

>>106998851
Besides saving bandwidth/space it supports lossy transparency with lossy compression, which is a thing we currently don't have.

Personally users don't really benefit from Webp because storage is very cheap now. Bandwidth for websites however, continues being a huge burden which is why they're switching to Webp.

webp is incredibly inefficient. efficiency doesn't begin and end with GOOG's data fees.

>>106998983
How is 20-30% better compression efficiency over JPG "incredibly inefficient"? Like I get hating Webp because fucking 4chicanery doesn't support it despite gorrillions of other websites adopting it

BUTT

On average when you take into account photographic images AND chinese cartoon ones you hit 20-30% better compression efficiency over JPG.

Like AFAIK that's what Google measures in their test. You can easily fudge the numbers to like 50% better compression efficiency if you only look at chinese cartoon sources and unfairly shill Webp but that's not what Google did.

I don't even like google, Android has gone to shit but you're making me defend them you fucking imbecile.

>>106996328 (OP)
the fact that the creator of 4chan is called an hero always cracks me up

>>106999787
> “Everybody’s doing it”
Ok guy.

It’s inefficient because it take more computation.
Also, it’s unnecessary.
Google burns more data with angular in a single day than webp will ever save in it’s entire history.
Get educated before you start shilling.

>>106999901
>It’s inefficient because it take more computation.
That's more tricky to answer because YES, hardware accelerated JPG encoders will leave Webp in the dust. However their compression efficiency is also really dogshit so Webp ends up with 40-60% better compression efficiency instead of just 20-30% vs nvjpeg.

Can Webp's huge compression efficiency over nvjpeg make up for the latter churning 6 million JPG images per hour? I dunno.

>>106999957
forgot source

https://developer.nvidia.com/nvjpeg

>>106997568
webp only supporting 1 type of chrome downsampling is the reason why it will always remain the designated shitting format.
It is a shame about the lossless version, which is probably the best lossless format we have. AVIF is huge step back on that front.

>>107000388
To be fair this is gradually becoming more of a boomer talking point because chroma sub sampling artefacts are harder to identify in high density displays like those found in modern day laptops/tablets/phones.

>>106996328 (OP)
they support webm which for all intents and pruposes is a "colleciton" of webp. each frame is rendered using vp8/vp9 and a webp is rendered with the same codec. so each frame in a webm is rendered in the same way a webp is. make it make sense.

>>106996357
Why? That's literally the reason why people who frequently use this website hate this format

>>107000447
It is irrelevant if you consider cacheslop quality to be webp's only objective -- which it is.
But yeah, it will also never be popular because nothing supports it. Also generation loss in webp is abysmal.

>>107000490
NOT REALLY. VP8 and VP9 have full blown hardware decoding but Webp does not. Webp is like a + version of VP8 that never got hardware acceleration. For example it has an adjustable macroblock filtering option to control how much Webp turns images into melted butter (default settings are unsurprisingly terrible).

>>107000531
It is VERY relevant because there were virtually 0 commercially affordable high density displays around 2010 when Webp was released. Thus the chroma artefacting was very obvious.

Fast forward to 2025 and for around $100, 90% of poorfags can now purchase a tablet with a 200+ PPI display.

>inb4 "you don't need more than 720p on a tablet"
Get glasses already, jesus christ.

I think it would be nice to use 4chan without seeing CSAM being posted in random threads. Not sure what’s going on. Is the site going to get shut down?

>>106996328 (OP)
Once WebP images started working on my machine & my photo manager started handling them I really turned around on WebP. It's nice having a 40% space saving lossless image compared to png. Now I just wish I could use them anywhere.
What we really need is jxl, that's another good format.

>>107000825
God willing.

>>107000876
JXL is a bit of IFFY format. Like it's great but the computational leap in encoding/decoding is pretty brutal. Could change in another decade if CPU advancements don't stagnate.

>>107000898
I just like the features, if it gets major adoption people will figure out acceleration I'm sure.

>>107000924
I wouldn't hold my breath. I just recently bought an Android 15 phone. Cocksucking piece of shit doesn't have AV1 hardware decoding. Whoever decided to save $0.10 of silicone deserves to be jobless desu.

>>107000935
Android TV is even worse, some of them can't even handle h264 or h265.
t.hosts a jellyfin instance

>>107000948
h265 I can understand due to kike fees but no h264 should be investigated by consumer protection committee or whatever. The again that orange white nigger probably cut funding to that to allocate more money to israel...

>>106996428
>>106996670
anyone who mentions jpeg 2000 is trolling

>>106996328 (OP)
why must you shill proprietary google formats?

>>106996328 (OP)
Wait until you hear about avif....
Javascript buddies like you should be [redacted] *toilet flushing*

>>106998970
Storage isn't a problem for 4chins because it deletes old threads. Unlike some other abominations.
If I had an imageboard it would self destruct any threads older than 24 hours. So long containment generals and discord faggots.

>>106996428
>We recently got H264 support instead of AV1
H264 is better than AV1. AV1 is a cancer trash format that consumes a lot of CPU. Vp8 sucks and VP9 is basically just a shittier version of AV1.
What really should happen is Poogle and Pozilla add support for H.265 into browsers so we can use that too.

>>107000736
>VP8 and VP9 have full blown hardware decoding but Webp does not
hardware decoding for an image is not efficient because you have to pass data between cpu and gpu and that has setup time and overhead. the only reason hardware decoding works for videos is because you can pass big batches of data at once and have the gpu crunch it.

>>106997505
i don't care if it's more efficient. almost no software or websites supports it.

>>107002316
it's not proprietary

>>106996357
Fibipipy
/thread

>>107001448
I find it plausible desu. H264 was being requested by NO ONE and we got that piece of shit and the awful quality degradation of video with it as well because IN THEORY it was going to allow twitter screen shit videos to be posted here but the cocksucking file upload limit remained 4MB so people just recompress the 10-20 MB twitter screen shit videos to 144p with H264 instead.

>>107002343
>t. boomer with swiss cheese brain from being a raging alcoholic

https://goughlui.com/2024/02/25/video-codec-round-up-2023-part-18-conclusion/

>>107002342
It's not but bandwidth is. Sayyy AN HIRO did do the reasonable thing and increase the upload limit to 20MB to compensate for H264's SHIT compression efficiency. Everything would load slow as fuck because given the April hack, 4chan is like really really poor. The passes barely make a dent given the abysmal arguably non-existent 4chan dev team.

>>107002343
>AV1 is a cancer trash format that consumes a lot of CPU.
It's not 2020 anymore DOUGH. Encoding AV1 video is now literally faster than encoding H264 video.

https://desuarchive.org/g/thread/106327782

>>107002343
>What really should happen is Poogle and Pozilla add support for H.265 into browsers so we can use that too.
You have to pay a kike fee to use this shit thing that takes forever to encode. Meanwhile AV1 costs $0 to use and encodes faster. Get your mpeg-la kike shit out of here.

>>107003703
Well, decoding it still somehow eats up CPU on Jewtube. I use an extension that forces it to give me h264 video so it can use hardware acceleration.
I don't care about CPU usage on my desktop but on my laptop I dont want it wasting all my battery because some Googlejeets wanted to cheap out on licensing fees.

>>107000501
Windows 7 can't natively open them.

>>107003934
That's kinda fair but unless you have a sandy birdge, software decoding AV1 isn't going to have that much of an effect on battery life. Modern day CPUs can decode 500+ FPS of AV1 video so your CPU spiking to 20% idle instead of 10% idle might knock of an hour of battery life at worst.

>>107004040
Yeah so why should I accept a jump in cpu package power usage from 3 watts with hardware acceleration to 4.5 watts without it just to be able to use a shitty Freetard codec? My network bandwidth is unlimited, my battery life is not. Seems like a very simple decision to me.
Now maybe if I was on some shitty satellite internet with limited data or really slow speed then I would start downloading AV1 instead of H.264.

>>107004088
Yeah, I can relate to that mein fuhrer. But it's kinda nice to stick it to the mpeg-la juden by adopting AV1. Even though H264 is now patent free it still feels jewish to use imho.

boommmmping this thread because other OP deserves aids

>>107004039
>My deadshit OS cannot support this format therefore, I'm entitled to have everyone else not support it as well

Also anybody using jpegli yet? Kinda makes Webp obsolete IMHO.

We'll get webp after av2if is old and busted.

this logo fucking sucks it looks like it says "webop"

>>106996328 (OP)
>backdoored by google

>>107002414
Kotoba to live by desu

>>106996357
This. Fuck this meme format

>>106996328 (OP)
regardless of how efficient webp is, this is 2025 and we have GBPS internet and terrabytes of storage. Google can suck my taint webp sucks dick. This isnt 1990 who gives a fuck how much ram this jpeg is going to consume, chrome is already consuming 20 GB

>>107002462
but it is, maybe not definition, but by design
it's owned by google and the only existing implementation is by google and they can make any changes they want to it
stop shilling billion dollar corpo slop
look where it got us with chrome market share, again, "open source" but actually proprietary in practice

>>106996328 (OP)
>WHEN WILL YOU SUPPORT GOOGLE PRODUCT SAAAAAAR???????
Kill yourself