It's important to note that Google will continue to require AMP for things like swiping up to see the page an image search result comes from.
This is more able to be fairly rationalised, I believe, because it relies on technical improvements that AMP offers beyond speed, like static layout.
Still, I don't see why whether a page implements AMP is the only way Google can make that decision. Google already measures cumulative layout shift: https://web.dev/vitals/.
I think it's clear from everything Google has done and how they've pushed AMP that one of their goals is to get people to use AMP in particular, as opposed to get people to make mostly static, fast websites. And as we've seen, if huge swathes of the web feel compelled (or forced) to use AMP, it affords Google a massive amount of power over how people consume content on the web.
It's important to note that Google will continue to require AMP for things like swiping up to see the page an image search result comes from.
This is more able to be fairly rationalised, I believe, because it relies on technical improvements that AMP offers beyond speed, like static layout.
Still, I don't see why whether a page implements AMP is the only way Google can make that decision. Google already measures cumulative layout shift: https://web.dev/vitals/.
I think it's clear from everything Google has done and how they've pushed AMP that one of their goals is to get people to use AMP in particular, as opposed to get people to make mostly static, fast websites. And as we've seen, if huge swathes of the web feel compelled (or forced) to use AMP, it affords Google a massive amount of power over how people consume content on the web.