April 23, 2026
Lazy images, heated takes
The End of Responsive Images
Confession! Dev says “auto” fixes images; commenters roast, toast, and demand magic
TLDR: A web standards veteran says new browser features—automatic image sizing and lazy loading—make complex image code less necessary. Comments split between relief and skepticism: some demand futuristic resizing like seam carving, others call it a stopgap, and a few say the real fix is smaller, better‑compressed images, period
A web standards veteran just dropped a plot twist: he helped create the confusing responsive image code we’ve all wrestled with—and he hated it. His big reveal is delightfully boring: browsers now do more of the heavy lifting with sizes="auto" (the browser picks the right image size) and loading="lazy" (don’t load pictures until you scroll), promising faster pages with fewer headaches.
The comments? A popcorn buffet. DonnyV wanted sci‑fi image magic, fuming that no one mentioned “seam carving,” and linking a wild demo of intelligent resizing: js-image-carver. Markstos played hall monitor with a tidy recap: the author loves auto sizing and lazy loading. But mrbluecoat delivered the side‑eye of the day—“14 years for this?”—calling the new setup “more like a polyfill” than a permanent fix.
Then came the roast. flufluflufluffy called out the author for saying “we’re not here to talk about picture” and then, well, talking about it—at length. AlienRobot waved off the drama with “just img { width: 100%; height: auto; },” dunking on sites that still ship giant, uncompressed PNGs. Translation: the vibe is equal parts Finally, sanity, Where’s the moonshot, and Please, for the love of bandwidth, stop shipping huge images. The only consensus? Images still dominate page weight—and now the browser might finally help carry it.
Key Points
- •The author led efforts as Chair of the RICG to standardize responsive image markup on the web.
- •A community campaign worked with browser vendors over years to create a workable responsive image syntax.
- •Adoption was driven by funding independent browser implementations, building polyfills, and integrating with major CMSs.
- •The author acknowledges widespread developer frustration with srcset selection logic and generating accurate sizes values.
- •The push for responsive images addressed a major performance issue: images constitute a large share of web transfer size, and flexible layouts otherwise force oversized assets.