Live data from Hacker News

I decided to disable AMP on my site

alexkras.com

131–140 of 360 posts

Re: I decided to disable AMP on my site

#131

Earlier quoted context omitted.

Completely agree, while technically AMP is suitable but it creates a walled garden by using Google - who actually boost page rankings if you use it, so they have publishers by the balls "forcing" them to use AMP to get higher in their rankings.

who actually boost page rankings if you use it No they don't. The news carousel prioritizes AMP, but it has no known measure on search engine results. AMP chatter on here has become incredibly one-sided to the point of absurdity, where karma is easily gained by denigrating AMP, talking about "leaving" it, etc. It is beyond reasoned discussion.

The carousel is the top result.

Re: I decided to disable AMP on my site

#133

In the 90s web pages loaded instantly. Now we have faster computers and faster networks, but apparently we need something like AMP to make the web fast. We have regressed.

We've lived through different 90s then. Most of my early porn was loading for ages, first appearing partially, then slowly loading the rest, to finally display a 600x400 (full screen!) image. Well, I was rather young then, so one image was often enough, and the waiting time made it all the more... satisfying, but it sure as hell wasn't "loaded instantly" :)

I'm not talking about downloading images. I'm talking about web pages that contain information. Reading news, recipes etc.

Re: I decided to disable AMP on my site

#134

Earlier quoted context omitted.

Yes, but still implemented non-natively -- along with all kind of other bizarro differences that might be lurking.

No, AFAIK the only reason that view had different scrolling was because it was an overflowing div which had the -webkit-overflow-scroll: touch property to give it any momentum. This page should demonstrate the same scrolling behaviour as AMP pages on iOS, without any 'custom' non-native scrolling https://s.codepen.io/joshhunt/debug/Xgeyoo

I worked on a website that experienced this same problem several years ago. The designers were pretty insistent on a design that would require the crappy non-native scrolling, but luckily management stepped in and said no to them.

Point being, UX should dictate design, not vice-versa. If you can't implement something the way you want without messing up something as important as scrolling then don't do it.

The irony here is that the two most important features of the web are arguably URLs and scrollable pages. And AMP screwed up both of them.

Re: I decided to disable AMP on my site

#135

In the 90s web pages loaded instantly. Now we have faster computers and faster networks, but apparently we need something like AMP to make the web fast. We have regressed.

Those are some extremely rose colored glasses you are wearing if you think web pages loaded instantly in the 90's I remember using the web on a 56k modem (which was pretty damn fast!) and waiting 30+ seconds for pages to fully load.

Of course 56k was slow. It's 56k. But if you ever used a faster line in the 90s it was virtually instant. Everyone has those faster lines now, but it's never instant.

Re: I decided to disable AMP on my site

#136

Earlier quoted context omitted.

who actually boost page rankings if you use it No they don't. The news carousel prioritizes AMP, but it has no known measure on search engine results. AMP chatter on here has become incredibly one-sided to the point of absurdity, where karma is easily gained by denigrating AMP, talking about "leaving" it, etc. It is beyond reasoned discussion.

The carousel is the top result.

The carousel is only for news/trending type searches. The fact that we're all to just pretend like everything people search for is news/trending is exactly the sort of nonsense that makes discussing AMP futile on here.

Re: I decided to disable AMP on my site

#137

The author has some very valid points against AMP from a technical standpoint, but for me there is a single reason that is sufficient: the Web is, and should stay, free and open . Indeed, I'm having really hard time trying to understand how people can be fine with AMP while fighting for the net neutrality and so on.

[deleted]

Re: I decided to disable AMP on my site

#138

AMP news articles lack comments. This is often were most of my interest lies. I want to see if anything in the article is called out in the comments.

I actually think suppressing comments (sometimes called "the sewer of the internet") is a feature, not a bug. I block Facebook comments using a Chrome extension mainly because I don't want to send huge amounts of information to Facebook when browsing random web pages, but not having to see the comments is also a bonus.

Re: I decided to disable AMP on my site

#139
post #21

> On iPhone, AMP seems to override the default browser scrolling. As a result scrolling of AMP pages feels off. Good news! iOS 11 fixes this. Safari actually has an inconsistent scrolling speed compared to the rest of the OS. iOS 11 makes all Safari pages scroll at the same speed as AMP sites (-webkit-overflow-scrolling: touch) Also important distinction for people to remember - AMP is two products: - CDN with preloa…

Re: two products, I realized this but never really thought about it. Can one self-host an AMP (framework) implementation? Does Google still promote such content, even if it isn't part of their CDN?

I actually converted my blog (http://dangoldin.com/) a while back to be entirely in AMP. In this way I'm using the framework without caring about the CDN element.

After reading this I may just bite the bullet and remove AMP and just cut out a bunch of crap to get it optimized for lower bandwidth devices.

Re: I decided to disable AMP on my site

#140
I've read quite a lot about AMP, but I still don't really understand for what technical reason a new markup language (AMP HTML) and an additional javascript library is required to achieve the (claimed) effect.

More specifically: Is there any evidence that AMP is able to provide a better result (at least in terms of performance) than just using a small subset of standard HTML, a little bit of CSS, getting rid of any javascript, and ensuring that the total page size is less than 100KB? If yes, I would be interested in the technical reasons.

Post reply on HN