Live data from Hacker News

The Problem with AMP

80x24.net

41–50 of 353 posts

Re: The Problem with AMP

#41
post #40
post #7

Earlier quoted context omitted.

You must have not wanted access to the site's full set of features, not wanted to use a mobile ad blocker, now wanted access to comments, etc. That's fine, but for many, it's an annoyance.

Comments are half the news anyways :)

So true

Re: The Problem with AMP

#42

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

But the people who designed the page in the first place should be able to make it just as fast without using AMP.

> But the people who designed the page in the first place should be able to make it just as fast without using AMP.

...but they don't, which is the point.

I'll throw my hat in on being a fan of reading news on AMP pages as well (though reddit amp does seem completely broken). I wouldn't care in the least if news site x instead wrote a fast site, I'd happily use that instead. But until they do, yeah, as a user I'll click on the amp link first.

Re: The Problem with AMP

#43
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 ?

I imagine it's supposed to be similar to how Apple's iAd platform works for iOS apps. It's a bad shake for third-party ad networks, but it's great for user privacy, since third-party origin requests are no longer being made to anyone but the platform owner (who then anonymizes the impression metrics they give back to the ad creators, who just have to trust the platform-owner's stats.)

Re: The Problem with AMP

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

Can you give an example of how to view reddit via AMP? If I just search for "reddit" on my Android phone for example, there are no AMP links to reddit, only Business Insider etc.

On my phone (chrome on android), basically any google search result from reddit goes to the amp version of the page.

(with all five visible comments, and since the full comments are almost certainly what I was searching for, I end up having to click through to the full page anyway every time)

Re: The Problem with AMP

#46
post #15

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.

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.

Re: The Problem with AMP

#47

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.

I believe the Google AMP CDN 'caching' is opt-in anyway

It's not. Google will cache all AMP pages.

Re: The Problem with AMP

#48

Is it possible to fork the project and keep all the good things that makes it fast but remove all the evil lock in stuff?

If you mean the Google CDN cache, just don't include the Google CDN file and host it yourself instead

Then google doesn't consider it a valid AMP file and won't give it the AMP tag. The spec literally requires you to use the CDN.

Re: The Problem with AMP

#49

Earlier quoted context omitted.

But the people who designed the page in the first place should be able to make it just as fast without using AMP.

> But the people who designed the page in the first place should be able to make it just as fast without using AMP. ...but they don't, which is the point. I'll throw my hat in on being a fan of reading news on AMP pages as well (though reddit amp does seem completely broken). I wouldn't care in the least if news site x instead wrote a fast site, I'd happily use that instead. But until they do, yeah, as a user I'll cl…

And I'm the opposite. I do my best to NOT use AMP pages. If a site can't be bothered to optimize it's own pages, then they don't get my attention/money/whatever. I can do without. Let the best developed sites win.
Post reply on HN