The end of responsive images
OuterVale
61 points
20 comments
April 23, 2026
Related Discussions
Found 5 related stories in 65.0ms across 5,406 title embeddings via pgvector HNSW
- Google Just Patented the End of Your Website bookofjoe · 39 pts · March 27, 2026 · 50% similar
- Prepping for the Endgame of the Open Web Brajeshwar · 23 pts · April 19, 2026 · 45% similar
- Celebrating Interesting Flickr Technologies steerpike · 14 pts · March 12, 2026 · 43% similar
- The CMS is dead, long live the CMS taubek · 132 pts · April 04, 2026 · 43% similar
- The death of social media is the renaissance of RSS (2025) jruohonen · 55 pts · March 09, 2026 · 42% similar
Discussion Highlights (8 comments)
DonnyV
I can't believe this doesn't mention Image Seam Carving. Surprise this was never built into browsers. https://trekhleb.dev/js-image-carver/
markstos
Summary: author is a fan of the new sizes="auto" and loading="lazy" browser features.
mrbluecoat
The author was waiting 14 years to excitedly share this? <img loading="lazy" src="TrIZjHKy9-650.jpeg" srcset="GTrIZjHKy9-650.jpeg 650w, GTrIZjHKy9-960.jpeg 960w, GTrIZjHKy9-1400.jpeg 1400w" sizes="auto, (min-width: 1040px) 650px, calc(94.44vw - 15px)" alt="…"> IMHO, feels more like a polyfill than a final industry solution.
flufluflufluffy
> We’re not here to talk about picture. Bro you just spewed 2 long paragraphs about picture at me. Don’t talk to me like that.
AlienRobot
On the other hand you could just img { width: 100%; height: auto; } and still have more performance than websites that just send uncompressed PNGs in the hero.
felooboolooomba
To the author: please consider putting a summary at top of the article.
tosti
What a lovely story. Sad to see the others don't like it. The most incredible thing is that a group of enthousiasts can join in the standards making process and actually move companies as big as Google and Apple. Even just a tiny bit.
keane
Key passages: > A few weeks ago, two patches landed in Gecko and WebKit… aligning [them] with Blink in supporting a relatively recent addition to the HTML specification: support for an auto value in sizes attributes. > [T]he central issue with srcset / sizes was one of timing: a browser makes decisions about image requests long before it has any information about the page's layout… That assumption is… still the default behavior: if there’s an img in your markup, the request it triggers will be fired off long before any information about the layout can be known > [T]hat is, unless that image uses the loading="lazy" attribute… [which] changes that entire equation — now those images are requested at the point of user interaction, long after the browser has all the information it needs about the sizes of the rendered image. The mdn page is https://developer.mozilla.org/en-US/docs/Web/API/HTMLImageEl... but what the mdn examples don't include is that the auto attribute can be used in addition to a specified sizes fallback. The Piccalilli article discusses this and includes example markup.