It's really something. It was using ~400Mbps of my mostly-idle 500Mbps connection (slow for some folks, but pretty speedy in my particular ghetto).

It appears that there are 62 videos on the page. They're generally 16fps and 60s long. All are h.264, 1280x704. The median bitrate is 4.962 Mbps.

I don't know enough about JS to try to understand WTF it is doing, but there's only 1.3 GB of video on that page. At a transfer speed of 400Mbps, the whole mess of them should be downloadable in around 30 seconds.

But it wasn't behaving that way at all. It instead behaved as an excellent bandwidth-waster.

(Woe to those who click this link on metered connection, I guess.)

They don't even notice it happening, it is not a conscious thought not to fix it.

Empathizing about problems you don't face is a hard product/ux and management skill. Facebook famously simulated 2G on Tuesdays 10 years ago[1] for example to get their employees to see the problems their users have.[2]

People don't to put effort in noticing(solving comes next) problems they don't face. It is why things like a11y and i18n need regulation like ADA etc.

[1] https://engineering.fb.com/2015/10/27/networking-traffic/bui...

[2]While it would be hard to attribute directly, GraphQL and to an extent React probably was influenced by these kind of things

> Are AI researchers so used to burning through compute and network resources that they don't stop to think about a webpage that will autoplay and loop multiple HD videos?

I’m sure they’ll give their Claude instance a stern talking-to.

Nearly every website for papers about AI applied to graphics hangs my phone browser, so I'm assuming the answer's yes.