> the page you're reading now is ~2.2MB, which is in line with typical page weights of ~2.7MB these days

For a small mostly-text blog post? Wtf are you talking about? That’s absurd.

This page has PNGs that need serious optimization. On my monitor, those 2 Cloudflare page screenshots are ~2000x1000 PNGs that weigh 700k each. They occupy about 850x500 "px" on my monitor. (The logo and author pic are likewise, ~300x300 PNGs downscaled to ~40x40.) Serving lossy images at such high resolutions sorta makes sense, but with PNGs they kill page load times. These images could probably get away with a lossy format and much lower resolution, and the page would be less than half the size it is now.

Wow what a fun little interesting time. My wife and I made it to the end on mobile!

Why would it?

Because this piece made the rounds recently https://www.bloomberg.com/opinion/articles/2023-05-08/oil-co...

It uses the same library as glow (glamour) -

https://github.com/cli/cli/blob/e876b229634b02d40bdfbb15844d...

And from 2010. I missed both facts despite reading the whole darn thing.

Proud of myself for recognizing the conceit (pun intended) here pretty quickly. Good point in the end too!

Did google get slashdotted by hacker news? The “getting started” link at the bottom gives me an internal server error.

While the original site isn’t feeling well: https://archive.md/YV9AQ

I wasn’t able to view the content with this link. I tried using the captcha but it kept unchecking itself. I’m on mobile so I couldn’t debug.

I enjoyed this. In particular the drawn diagram and:

> Look at an audio file's waveform before playing it at max volume.

That’s always good advice.