So, you want to push a web platform feature?| blog.yoav.ws
Improving language negotiation| blog.yoav.ws
How Chromium's cookies get evicted| blog.yoav.ws
On resource bundling and compression dictionaries| blog.yoav.ws
Skiing| blog.yoav.ws
Why Chromium cares about standards| blog.yoav.ws
Task Attribution Semantics| blog.yoav.ws
First post ever| blog.yoav.ws
Responsive images - hacks won't cut it| blog.yoav.ws
How Big Is Art-Direction?| blog.yoav.ws
UA spoofers have feelings too!| blog.yoav.ws
I think it really depends on the actual website you're working on. That's the problem with many things on the web, there's just not one right answer to any problem. Context is everything.| blog.yoav.ws
My take on adaptive images| blog.yoav.ws
Simpler responsive images proposal| blog.yoav.ws
Preloaders, cookies and race conditions| blog.yoav.ws
Unblocking blocking stylesheets| blog.yoav.ws
Responsive image format| blog.yoav.ws
Images. Can we have less?| blog.yoav.ws
Fetching responsive image format| blog.yoav.ws
Who Is Sizer Soze?| blog.yoav.ws
Responsive Image Container| blog.yoav.ws
Long Overdue| blog.yoav.ws
Deprecating HTTP| blog.yoav.ws
By the people| blog.yoav.ws
Adapting without assumptions| blog.yoav.ws
Being Pushy| blog.yoav.ws
TPAC 2016 report| blog.yoav.ws
A Tale of Four Caches| blog.yoav.ws
Google| blog.yoav.ws
WebPerfWG F2F summary - June 2019| blog.yoav.ws
So, you don't like a web platform proposal| blog.yoav.ws