AMP made some technical sense to speed up page load but it’s proprietary nature and the available http3 and quic protocols mean that It’s high time to say goodbye to amp pages.
> The speed benefits Google marketed were also at least partly a result of Google’s
throttling. Google throttles the load time of non-AMP ads by giving them artificial one-second
delays in order to give Google AMP a “nice comparative boost.
The stated goals of AMP made sense. But the technical specifics made things feel much slower. Specifically the requirements around a single draw meant waiting on a white screen for everything to load before showing anything. In contrast, normal pages that render as they go lets you start using the page before everything finishes. It's not great when the page changes drastically as it loads, but you can acheive a page that doesn't jump around (or doesn't jump around much) as it loads without forcing a single render.
Only tangential but the only time I really fly into a rage at tech anymore is when a (mobile) website uses the dark pattern of placing a link somewhere where 0.25 sec after load it will be moved down by an ad. When it happens I attempt to click the link, click the ad instead, hit back, and hit the ad a second time. Usually, I'll back out of whatever site this happens on and never go back.
Yeah... that's super annoying... there's maybe some exceptions, but it's usually not that hard to at least just put a height on the ad, so it's a blank rectangle until it finishes loading, and then it's an annoying rectangle, but it doesn't need to change shape.
Also, on my hate list, articles with an ad under a paragraph that somehow moves to the top when it gets half-way up the screen or something, so it's really hard to scroll down while reading. Blerg.
