Alex MacArthur
@macarthur.me
Bossing around computers in made-up languages.
Further confirmation of my point. ✅
June 18, 2025 at 10:49 PM
Further confirmation of my point. ✅
much appreciated, @andrejnsimoes.com + @gregex.bsky.social!
June 3, 2025 at 2:32 PM
much appreciated, @andrejnsimoes.com + @gregex.bsky.social!
- The lighter, resized images will be served for future page views.
I've seen many, many examples of 3000px-wide images being used for a small 300px-wide card. Now you don't even need to think about it.
Just plop a small, deferred, non-intrusive script pages with PP images. ⚡️
I've seen many, many examples of 3000px-wide images being used for a small 300px-wide card. Now you don't even need to think about it.
Just plop a small, deferred, non-intrusive script pages with PP images. ⚡️
April 15, 2025 at 12:19 AM
- The lighter, resized images will be served for future page views.
I've seen many, many examples of 3000px-wide images being used for a small 300px-wide card. Now you don't even need to think about it.
Just plop a small, deferred, non-intrusive script pages with PP images. ⚡️
I've seen many, many examples of 3000px-wide images being used for a small 300px-wide card. Now you don't even need to think about it.
Just plop a small, deferred, non-intrusive script pages with PP images. ⚡️
- Each image will be measured, using the rendered & natural widths to determine if it could be resized more effectively.
- Eligible images will be asynchronously resized based on how they *actually* show on a large screen.
- Eligible images will be asynchronously resized based on how they *actually* show on a large screen.
April 15, 2025 at 12:19 AM
- Each image will be measured, using the rendered & natural widths to determine if it could be resized more effectively.
- Eligible images will be asynchronously resized based on how they *actually* show on a large screen.
- Eligible images will be asynchronously resized based on how they *actually* show on a large screen.
