Viewing profile — 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…

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.

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

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 abo…

iirc, back in ~99, Unreal Engine was doing dithering on the u/v coordinates (!!) for texture mapping instead of bilinear interpolation. They used fixed Bayer matrix. This was quite…

[one of WebP2 author here] This 'new' WebP format is not radically different, but just pushes the same use-cases further (The web. Not archival. Not camera capture.), sticking to s…

video format usually take up too much memory: what you gain in efficiency costs in resources. Conversely, animated WebP are dirt cheap: one buffer only, written over and over. Then…

WebP version 2 is in the work at AOM: https://www.youtube.com/watch?v=zogxpP2lm-o It is complementary to AVIF (which targets photo capture more than delivery over the web). WebP2 i…