3 ms·

As a user and as a non-monetizing publisher I love AMP. It's fast, offers free caching, and gives users a positive experience. I don't get the hostility toward

As a user and as a non-monetizing publisher I love AMP. It's fast, offers free caching, and gives users a positive experience. I don't get the hostility towards AMP, or the outright obnoxiousness of people who are against it (the replies to someone who works on AMP are so uncharitable and hostile). There are downsides, and I do wish the alternative was simply a "HTMLite" that standardized many of the restrictions of AMP to stop it from being the tragedy of the commons that many publishers make it, but it's hardly the villain its held as.

geocar 9y ago
As a publisher who has some properties with ads and some properties without, I get the stickiness complaints. I don't implement AMP simply because it's time spent that offers me nothing -- my sticky and converting traffic doesn't come from organic google search anyway. > There are downsides, and I do wish the alternative was simply A simple alternative would be public content caches; a meta tag that says "prefetch me" is a way for the publisher to tell sites it's okay to prefetch it and store the content in the content caches. I think trusting a google-run content-cache with no cookies would be easy for browser manufacturers to implement. It also wouldn't affect the user interface adversely. A separate, unrelated program could be used for the "fast" logo that would require all/most content on public caches and pageload fired in under 0.5sec (or some other metric).
ezfe 9y ago
I am hostile towards AMP because the benefits it gives are overrated and easy to achieve if you know what you're doing. AMP is designed to strip down the complexity and make pages small so they load fast (yes, there's more to it, I know), which is something that can be done with a little bit of knowledge about how page loading and resources work. AMP is marketed as a pre-requisite for fast site loading, when in reality it's just one in many ways to achieve that. But with this ideology, Google prioritizes AMP pages because they must be the fastest, and they hijack the URLs on Mobile, again all in the name of Speed, but at what cost.
- recursive 9y ago
  As a user, when faced with a hyperlink, there's really no way to know if the website on the other end of that link is operated by someone who "knows what they're doing". Part of AMP is the little icon next to the hyperlink, which acts like a certification.

geocar 9y ago

As a publisher who has some properties with ads and some properties without, I get the stickiness complaints. I don't implement AMP simply because it's time spent that offers me nothing -- my sticky and converting traffic doesn't come from organic google search anyway. > There are downsides, and I do wish the alternative was simply A simple alternative would be public content caches; a meta tag that says "prefetch me" is a way for the publisher to tell sites it's okay to prefetch it and store the content in the content caches. I think trusting a google-run content-cache with no cookies would be easy for browser manufacturers to implement. It also wouldn't affect the user interface adversely. A separate, unrelated program could be used for the "fast" logo that would require all/most content on public caches and pageload fired in under 0.5sec (or some other metric).

ezfe 9y ago

I am hostile towards AMP because the benefits it gives are overrated and easy to achieve if you know what you're doing. AMP is designed to strip down the complexity and make pages small so they load fast (yes, there's more to it, I know), which is something that can be done with a little bit of knowledge about how page loading and resources work. AMP is marketed as a pre-requisite for fast site loading, when in reality it's just one in many ways to achieve that. But with this ideology, Google prioritizes AMP pages because they must be the fastest, and they hijack the URLs on Mobile, again all in the name of Speed, but at what cost.

recursive 9y ago
As a user, when faced with a hyperlink, there's really no way to know if the website on the other end of that link is operated by someone who "knows what they're doing". Part of AMP is the little icon next to the hyperlink, which acts like a certification.