Comment by archerx

Comment by archerx 6 hours ago

Google created webp and that is why they are giving it unjustified preferential treatment and has been trying to unreasonably force it down the throat of the internet.

adzm 5 hours ago

WebP gave me alpha transparency with lossy images, which came in handy at the time. It was also not bogged down by patents and licensing. Plus like others said, if you support vp8 video, you pretty much already have a webp codec, same with AV1 and avif

Reply View 4 replies

archerx 4 hours ago

Lossy PNGs exist with transparency.

Reply View | 3 replies
- adzm 3 hours ago
  
  Do you mean lossless? PNGs are not lossy. A large photo with alpha channel in a lossless png could easily be 20x the size of a lossy webp
  
  Reply View | 2 replies
  
  Semaphor 2 hours ago
  
  PNG of course can be lossy. They aren’t great at it, but depending on the image can be good enough.
  
  Reply View | 0 replies
  
  archerx an hour ago
  
  No I meant lossy. This is the library I use; https://pngquant.org/
  
  Reply View | 0 replies

breppp 5 hours ago

unjustified preferential treatment over jpegxl a format google also had created

Reply View 4 replies

archerx 5 hours ago

They helped create jpegXL but they are not the sole owner like they are with webp. There is a difference.

Reply View | 3 replies
- breppp 4 hours ago
  
  a better argument might be that chrome protects their own vs a research group in google switzerland, however as other mentioned the security implications of another unsafe binary parser in a browser is hardly worth it
  
  Reply View | 2 replies
  
  archerx 4 hours ago
  
  Webp has had major vulnerabilities.
  https://blog.cloudflare.com/uncovering-the-hidden-webp-vulne...
  
  Reply View | 1 reply
  
  breppp 2 hours ago
  
  which only strengthens my argument, webp seemed like some ad-hoc pet project in chrome, and that ended like most unsafe binary parsers, with critical vulnerabilities
  
  Reply View | 0 replies

MrDOS 4 hours ago

You're getting downvoted, but you're not wrong. If anyone else had come up with it, it would have been ignored completely. I don't think it's as bad as some people make it out to be, but it's not really that compelling for end users, either. As other folks in the thread have pointed out, WebP is basically the static image format that you get “for free” when you've already got a VP8 video decoder.

The funny thing is all the places where Google's own ecosystem has ignored WebP. E.g., the golang stdlib has a WebP decoder, but all of the encoders you'll find are CGo bindings to libwebp.

Reply View 1 reply

archerx 4 hours ago

I noticed Hacker news is more about feelings than facts lately which is a shame.

Reply View | 0 replies