Yoav's blog thing

Why am I investing time and effort into WebMCP?

A guide for pushing new features into standards and browser engines

Discussion around the status quo of language negotiation on the web, a recent Chrome proposal and how I think we can do better.

A quick note on Chromium's cookie eviction mechanisms

Why compression dictionaries will force us to rethink our bundling strategies and their naming

On self-fulfilling prophecies and breaking them.

Me trying to explain why standards matter to Chromium, and why we do the things we do as part of the Blink process.

Tasks can be complex! This post discusses the attribution of different tasks on the web, and the different kinds of attribution one may want, and how to tell them apart.

How can you influence the web platform so that a change you don't like is less likely to get shipped?

The Web Performance Working Group had a face to face meeting. We talked about memory reporting, scheduling, CPU reporting and SPA metrics!

I'm joining Google to work on Chromium and web standards full time!

What caches does a request go through on its way to find its response and eternal happiness?

What is the one use-case where HTTP/2 server push shines over the alternatives?

Content adaptation is cool! This post discusses the different dimensions of content adaptation and the benefits of providing developers with access to them.

The web platform belongs to all of us. The Web Platform Incubator Community Group, or WICG, gives you a voice and a safe place to contribute to it.

Plain-text HTTP needs to die, but denying new feature support from it does not provide the right incentives.

I should write more!!

Experiments with a prototype for a responsive image container format.

How many bytes can you save by making your images responsive?

Some data gathering about the art-direction use case and its usage in the wild.

How could we have fetched a responsive image format, if we had one?

There's a lot of image data out there. Better compression can significantly reduce it!

Maybe progressive JPEGs are the responsive image format we've been waiting for all along?

A neat trick that can help make your blocking stylesheets non-blocking!

Or: why you don't want to use cookies for responsive image content negotiation.

Yet one more responsive images proposal.

While responsive images hacks are neat, we need browsers to support native responsive images as a real solution to that problem.

Adding my own proposal to the responsive images proposal flood.

How can we get rid of old IEs?

UA sniffing is bad, mmmkay?