The Problem with AMP • Hacker News Board

Re: The Problem with AMP

#11

Post by rashkov » Tue, Jan 17, 2017, 2:36 AM UTC

freyir wrote: post #6

AMP 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

#12

Post by tschellenbach » Tue, Jan 17, 2017, 2:36 AM UTC

It's actually a pretty nifty feature when you're browsing the web from a plane's slow wifi.

Re: The Problem with AMP

#13

Post by jey » Tue, Jan 17, 2017, 2:36 AM UTC

There's definitely something wrong with Reddit's AMP implementation.

Re: The Problem with AMP

#14

Post by freehunter » Tue, Jan 17, 2017, 2:36 AM UTC

robryan wrote: post #8

AMP is okay for news, but terrible for other forms of content. The reddit implementation is way less usable on mobile than going to their actual site. It also results in lower quality news appearing at the top of searches in cases where they have implemented AMP and the better sources haven't.

Man trying to go back a page on Reddit then clicking a link on that page and seeing "there was an error, please reload the page" gets me out of there so damn fast.

Re: The Problem with AMP

#15

Post by 65827 » Tue, Jan 17, 2017, 2:39 AM UTC

It's so strange to see Google repeating all the same mistakes AOL did so many years ago. No I don't want your fucking garden, I want the network. If you get in the way of that I'm done with you.

Re: The Problem with AMP

#16

Post by mrfusion » Tue, Jan 17, 2017, 2:40 AM UTC

Do the amp links from google results to Reddit seem broken to anyone else?

Edit: sorry that was actually in the article.

Re: The Problem with AMP

#17

Post by abusque » Tue, Jan 17, 2017, 2:42 AM UTC

Possibly 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/zYDZrtr.png

Re: The Problem with AMP

#18

Post by conductr » Tue, Jan 17, 2017, 2:43 AM UTC

On AMP page, clicking the X on the header box should load the HTML page. Instead it kicks you back to the search results. I think I would be okay if they fixed that one thing.

Re: The Problem with AMP

#19

Post by bluejekyll » Tue, Jan 17, 2017, 2:43 AM UTC

I 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

#20

Post by dzhiurgis » Tue, Jan 17, 2017, 2:46 AM UTC

So the argument against AMP is someone's broken implementation and "security" of Google's CDN. Sounds like terrible arguments.

That said, Google should give option to opt-out from CDN caching (if they don't already) as otherwise implementing AMP gives Google the right to host your content on their domain.