AMP is fast because it prerenders. That is the main point of AMP, and you seemingly don't understand it after working on it. It amazes me how little developers understand their platforms these days.
You may consider that we do understand pre-render, but don't like the trade-off involved.
A full on AOL style walled garden could be even faster. It could mandate brotli, force a common css base, only offer one kind of ad platform, etc. Should we go there?
The person I was responding to said that AMP was fast for a reason other than prerendering. That's wrong. Prerendering is the main point of AMP, which is what I pointed out in my comment.
A full AOL style walled garden is what Apple News and Facebook Instant Articles are. AMP enables the same speed in a way that any link aggregator can take advantage of without having to strike deals with individual publishers.
I agree with your literal statements, but Google does abuse AMP. The way they hijack left/right swipe and the back button for carousel loaded pages is ample evidence for me. It's very clearly not my content any more when you steal the top X pixels and hijack user interactions.
AMP also requires I include a Google owned and controlled piece of JavaScript that they can change at any time. That's literally in the "standard". In fact, a bad update borked all AMP pages for quite a while some time ago.
> The way they hijack left/right swipe and the back button for carousel loaded pages
This doesn't happen for me on any of my Android browsers. The problem is likely with your browser. I wouldn't be surprised if Chrome on iOS is buggy just like every other browser available for iOS.
> AMP also requires I include a Google owned and controlled piece of JavaScript that they can change at any time
If you don't want your page to load instantly from Google, Bing, and other link aggregators, don't use it. Same with Apple News, which has more ornery integration requirements. I, as a user, will simply skip over your links to find faster ones. If you don't give users what they want, what do you expect will happen?
> This doesn't happen for me on any of my Android browsers.
They're talking about a feature built into Safari on iOS that allows you to swipe between pages from the left and right edges of the screen. Since all browsers on iOS use Safari as the base, they will inherit this behavior unless they take specific steps to disable it, which most don't.
AMP breaks that behavior and although I don't use it, many many people on iOS do and are accustomed to it.
Yeah...my Google controlled browser that has dominant market share. Don't think Google wouldn't hijack on other browsers if they thought they could get away with it.
Please don't cross into personal attack. Your comment would be fine with just the first sentence, or if it stopped before "you seemingly". There's no need for supercilious disses of "developers" either.
That soyyo, like the article's author, seemingly does not understand that AMP enables prerendering is simply stating a fact. In soyyo's comment, there is no place where soyyo shows any understanding that this is the thing that AMP was designed to do.
When I continued with my general statement about developers not understanding their platforms, I can see how that can be interpreted as a personal attack, and for that I apologise to soyyo and to the readers of this forum.
A full on AOL style walled garden could be even faster. It could mandate brotli, force a common css base, only offer one kind of ad platform, etc. Should we go there?