There's two ways of setting a tone. One is to make the reader think/conclude a certain feeling. The second method is to tell them to feel the thing you want them to feel.
This article tells me to hype myself up, which had the exact opposite effect
As someone who has seen srcset and picture but never used them in practice, the background was kind of useful. but I can understand people finding it annoying
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.
This doesn't help you if you want to save bandwidth, it worsens it.
It doesn't help you if you custom-crop images depending on the viewport size, because if you go that far to art direct, then you're not going to like the result of automated and unsupervised seam carving.
Just publish 3 sizes, maybe crop the smallest one if the focus area is too small. Done.
Summary: author is a fan of the new sizes="auto" and loading="lazy" browser features.
thanks, i couldn't bother reading the thing due to the ridiculous chest-thumping and self-aggrandizing.
There's two ways of setting a tone. One is to make the reader think/conclude a certain feeling. The second method is to tell them to feel the thing you want them to feel.
This article tells me to hype myself up, which had the exact opposite effect
A picture is worth a thousand words; this article about pictures contains no pictures and too many words. Probably AI slop
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.
> 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.
As someone who has seen srcset and picture but never used them in practice, the background was kind of useful. but I can understand people finding it annoying
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.
I can't believe this doesn't mention Image Seam Carving. Surprise this was never built into browsers.
https://trekhleb.dev/js-image-carver/
I think this is far too risky.
This doesn't help you if you want to save bandwidth, it worsens it.
It doesn't help you if you custom-crop images depending on the viewport size, because if you go that far to art direct, then you're not going to like the result of automated and unsupervised seam carving.
Just publish 3 sizes, maybe crop the smallest one if the focus area is too small. Done.
I'd seen the technique, but never visualized like that. Very cool.