Live data from Hacker News

The Problem with AMP

80x24.net

81–90 of 353 posts

Re: The Problem with AMP

#81
post #29

One 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-…

Yeah but here it's functioning effectively as a better ad-blocker (one that doesn't screw up site layout). Looking at how AMP works, I can see why : you'd have to decide before you know who the user is what ads to show. Wouldn't that effectively mean that in a search query followed by an AMP site visit only Google has the opportunity to show targeted ads ?

That's not true. There is space in amp for a variety of iframe'd ad providers.

Re: The Problem with AMP

#82
post #69

Earlier quoted context omitted.

Everything seems to be moving towards gardens right now. Certainly not just Google. It's one of the things that depresses me most about tech right now.

The most depressing part of it is that the HN community don't seem to care and will actively cheer it in many cases (walled garden IRC and cloud in general). The only reason we have an open internet at all is because techies cared back in the day.

Internet is a co-operative anarchy: https://tools.ietf.org/html/rfc1726#page-5

Re: The Problem with AMP

#83

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.

That's my main pet peeve with AMP as well. In my mind the [x] in the top bar is almost exclusively associated with 'remove the bar' behavior in Safari on iOS.

Re: The Problem with AMP

#85
post #70
post #63

Earlier quoted context omitted.

I am really curious if an ordinary user gets frustrated with AMP as much as an HN reader does. PS: Not intending to be sarcastic. PS2: I work for google, but not on something amp related.

I've seen ordinary users get frustrated with it, but they don't understand why. They don't know what AMP is, and they don't realize they are on an AMP page. For example, the URL bar says they are on Google but they are reading a Slate article. The web is already confusing enough, and AMP makes it worse. Many ordinary users think they are reading content from Google, like that famous CNN interview where a lady said, "…

Ah I didn't know this.

I run a WordPress blog. From the documentations of Google and WordPress AMP plugins, I have always thought that the user will be directed to "originalurl/amp" on my domain when they click on the Google link on their phone. Now that I see it's a Google domain, this is really weird.

Re: The Problem with AMP

#86
post #69

Earlier quoted context omitted.

Everything seems to be moving towards gardens right now. Certainly not just Google. It's one of the things that depresses me most about tech right now.

The most depressing part of it is that the HN community don't seem to care and will actively cheer it in many cases (walled garden IRC and cloud in general). The only reason we have an open internet at all is because techies cared back in the day.

I feel like this is only partially true.

The majority of the articles, excluding those from large name corps, are simple loading pages. Using primarily the basic HTML and inline CSS. You do have the occasional blog page with some fancy touches, but the majority of the links that I click on while browsing HN has me questioning why, on sub par satellite internet, that HN and a majority of it's submitted posts work when Facebook, Google, Bing, etc.. does not.

I feel it can.

Everything just feels so bloated.

Re: The Problem with AMP

#87
post #70

Earlier quoted context omitted.

I've seen ordinary users get frustrated with it, but they don't understand why. They don't know what AMP is, and they don't realize they are on an AMP page. For example, the URL bar says they are on Google but they are reading a Slate article. The web is already confusing enough, and AMP makes it worse. Many ordinary users think they are reading content from Google, like that famous CNN interview where a lady said, "…

Ah I didn't know this. I run a WordPress blog. From the documentations of Google and WordPress AMP plugins, I have always thought that the user will be directed to "originalurl/amp" on my domain when they click on the Google link on their phone. Now that I see it's a Google domain, this is really weird.

It's not an AMP thing per se, it's how Google handles AMP in search results.

Re: The Problem with AMP

#88
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.

AMP is the reason why I stopped using Google News on mobile. They butchered again one of their product. I'm glad that RSS feeds are still a thing.

Re: The Problem with AMP

#89
post #70
post #63

Earlier quoted context omitted.

I am really curious if an ordinary user gets frustrated with AMP as much as an HN reader does. PS: Not intending to be sarcastic. PS2: I work for google, but not on something amp related.

I've seen ordinary users get frustrated with it, but they don't understand why. They don't know what AMP is, and they don't realize they are on an AMP page. For example, the URL bar says they are on Google but they are reading a Slate article. The web is already confusing enough, and AMP makes it worse. Many ordinary users think they are reading content from Google, like that famous CNN interview where a lady said, "…

> Which leads to the question, why is google doing this? They, you, could easily promote AMP pages while not masking the real URL!

Perhaps to allow the content to be served from a CDN (over HTTPS), without requiring the site to CNAME over their domain to Google.

If webmasters are willing to CNAME over their domain to a caching proxy, then a less intrusive design is possible[0], such as the one recently announced by Cloudflare[1].

[0]: https://github.com/ampproject/amphtml/blob/master/spec/amp-c... [1]: https://blog.cloudflare.com/accelerated-mobile/

Re: The Problem with AMP

#90

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.

That would likely confuse normal users more: "What do you mean I have to close the page to open the page properly?".
Post reply on HN