The Problem with AMP
51–60 of 353 posts
Re: The Problem with AMP
#52I wish the post offered an alternative. Given that there are at least three similar specs, shouldn't there be a Light HTML5, or something that provides the same set of underlying guarantees?
Re: The Problem with AMP
#53One thing I love about AMP, that seems to never be mentioned when people discuss it, is viewing AMP-HTML pages on my laptop. I wrote a small chrome extension that always forwards my page to the equivalent AMP page (if one exists) and the experience of reading the news is so much better. AMP pages off mobile are really really amazing. Compare Non-AMP[0] vs AMP[1] [0] http://www.sfgate.com/bayarea/article/Trump-on-the-…
edit: This is with an ad blocker on though.
Re: The Problem with AMP
#54I'm glad AMP's weaknesses are finally gaining attention and making their rounds. Google should not be allowed to steal publishers' traffic and strong-arm them into going along with it.
Re: The Problem with AMP
#55You can read more advantages at http://alphapages.io
Re: The Problem with AMP
#56The # 1 reason why AMP bothers me is when I want to share a link with someone, I don't want to send an AMP link.
Re: The Problem with AMP
#57Re: The Problem with AMP
#58AMP is one of the most frustrating experiences I've had with Google. the fact that it's foisted on users, with no option to disable it, makes it borderline infuriating. If you're stuck on an AMP page in your mobile browser, you can click on the browser's "Request desktop site" option to load the full page.
I get the frustration, but mobile sites in general also have this problem. "Request desktop site" should be a more prominent feature, at least in safari which is what I'm familiar with. It's quite buried unfortunately and I think that more non-techies would benefit from knowing about it.
Re: The Problem with AMP
#59AMP is one of the most frustrating experiences I've had with Google. the fact that it's foisted on users, with no option to disable it, makes it borderline infuriating. If you're stuck on an AMP page in your mobile browser, you can click on the browser's "Request desktop site" option to load the full page.
So you have to load the AMP page and then a potentially bloated normal page. That's AMP doing the exact opposite of it's intended (or at least stated) purpose. Noscript, flashblock and adblock have done far more for page speeds than than AMP ever will.
Re: The Problem with AMP
#60Possibly off-topic, but the article isn't displaying[0] for me on Chromium 55.0.2883.87 (64-bit), running on Arch Linux, unless I go in the dev tools and manually remove "Fira Sans" from the font-family list in .container[1]. Not sure whether the problem is with me or the site, I'm surprised it doesn't fall-back to sans-serif before I override manually. [0] http://i.imgur.com/qJKSvMC.png [1] http://i.imgur.com/zYDZrt…