| ▲ | The end of responsive images(piccalil.li) |
| 25 points by OuterVale 5 hours ago | 15 comments |
| |
|
| ▲ | markstos 3 hours ago | parent | next [-] |
| Summary: author is a fan of the new sizes="auto" and loading="lazy" browser features. |
| |
| ▲ | znort_ 3 hours ago | parent | next [-] | | thanks, i couldn't bother reading the thing due to the ridiculous chest-thumping and self-aggrandizing. | | |
| ▲ | ramon156 3 hours ago | parent | next [-] | | 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 | |
| ▲ | fmajid 41 minutes ago | parent | prev [-] | | He does ramble on and on about how awesome he is, and is enamored of the sound of his own voice. | | |
| ▲ | bensyverson 28 minutes ago | parent [-] | | I will say, it's now a little easier to understand why `srcset` and `sizes` are the way they are |
|
| |
| ▲ | xkcd-sucks 2 hours ago | parent | prev [-] | | A picture is worth a thousand words; this article about pictures contains no pictures and too many words. Probably AI slop | | |
| ▲ | zamadatix an hour ago | parent [-] | | Not everything you disliked reading is just probably AI slop https://piccalil.li/about/: > Workers first, AI technologies, dead last > AI and LLMs are rooted in theft, exploitation, dishonesty and are over-promoted with ill-intentions for workers. Instead of running towards AI, we’re focusing on what’s actually important: content that helps people to succeed that is never produced by AI tools. The style is definitely the over hyped and well expanded tone that AI is trained to mimic for sure though. |
|
|
|
| ▲ | mrbluecoat 3 hours ago | parent | prev | next [-] |
| 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. |
|
| ▲ | felooboolooomba an hour ago | parent | prev | next [-] |
| To the author: please consider putting a summary at top of the article. |
|
| ▲ | AlienRobot 2 hours ago | parent | prev | next [-] |
| 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. |
|
| ▲ | DonnyV 4 hours ago | parent | prev | next [-] |
| I can't believe this doesn't mention Image Seam Carving. Surprise this was never built into browsers. https://trekhleb.dev/js-image-carver/ |
| |
| ▲ | halapro 2 hours ago | parent | next [-] | | 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. | |
| ▲ | xnx 2 hours ago | parent | prev [-] | | I'd seen the technique, but never visualized like that. Very cool. |
|
|
| ▲ | flufluflufluffy 2 hours ago | parent | prev [-] |
| > 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. |
| |
| ▲ | Sivart13 2 hours ago | parent [-] | | 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 |
|