I think you could do foveated rendering efficiently with rasterization if you "simply" render twice at 2 different resolutions. A low resolution render over the entire FOV, and a higher resolution render in the fovea region. You would have overlap but overall it should be less pixels rendered.

Shadertoy got hugged to death by this shader a few years ago and it had a custom "please go away" banner for a little while. Funny seeing it show up again on HN front page.

https://web.archive.org/web/20210430091013/https://www.shade...

At 14:40 in the video they show the footage to a cop who's immediate reaction is

"To be honest with you. {talked over} you decide to change lane. How come you, did you think to change lanes or you just kinda froze up in that moment?"

He clearly thought they had plenty of time to react to it.

I don't see many people mentioning what to me is the largest cause of slow internet. A weak WiFi or 5G signal caused by being behind a brick wall or far away from the router.

This is the only reason I know why some websites/apps perform poorly on a bad connection (Discord struggles simply load the text content of messages).

Another one is being at a huge event with thousands of people trying to use mobile data at the same time.

If nothing else I think these two cases are enough to motivate caring a little bit about poor connections. Honestly I find them more motivating than developing for whatever % of users have a bad connection all the time.

It can absolutely be used to refactor and reduce code, simply asking "Can this be simplified" in reference to a file or system often results in a nice refactor.

However I wouldn't say refactoring is as hands free as letting AI produce the code in the first place, you need to cherry pick its best ideas and guide it a little bit more.