sk65535

you know, industry / browser people talk to each other. But not necessary on social media. Or publicly.

For a recap of WebP history: https://bit.ly/image_ready_webp_slides

If you look at slide #14, you'll see Opera was an early adopter. Firefox published a "No" blog-post in 2013, and Safari removed WebP support from Sierra preview in 2016, eventually adding it back in 2020. Stuff happened.

And yes, when WebP was created there was a real, non-incremental, need for a Web-oriented image format. Nowadays, it's just incremental improvement on this idea for browsers.

(disclaimer: WebP initiator here)

sk65535

há 5 anosdiscuss

AVIF is equivalent in decoding complexity, even in software. It's not order of magnitude different. Encoders OTOH can be as slow as you want them to be.

sk65535

há 5 anosdiscuss

if you re-arrange you have to wait for the bitstream to finish downloading, and thus lose the 'display something early on' feature.

sk65535

há 5 anosdiscuss

rule of the thumb: progressive JPEG costs ~3x more resources (CPU, memory) than baseline JPEG.

With baseline jpeg, you can blit the decoded blocks to screen directly and forget about it.

For progressive, you have to buffer the whole image (in DCT format!) and do the idct / color-space conversion on all passes.

Submissions

Latest Photoshop 23.2 supports WebP format natively

comments