Live data from Hacker News

The Problem with AMP

80x24.net

321–330 of 353 posts

Re: The Problem with AMP

#321

I make my own amp pages by keeping JavaScript turned off on my phone. 95℅ of pages work and load instantly. Those that don't, I turn on JavaScript. If I go to those pages a lot I add them to my exception list. Sorry but I'm not an amp believer.

It just took me 8 clicks and a couple swipes to disable JS in my mobile browser, Chrome on Android. Another 8 clicks and couple swipes to enable JS. Is there a faster way to do that?

[deleted]

Re: The Problem with AMP

#322

As described I don't believe I've ever seen an AMP'ified page as they're described?! Is it because I don't use Google as my goto search engine? (I use ddg almost exclusively.) Or, is it because I don't use Android Chrome as my browser? (I'm on Firefox Mobile unless some site owners forgot to test on Firefox and I'm forced onto Chrome.)

As far as I understand it, both of the above. AMP apparently doesn't work on Firefox and AMP-pages are only linked to by Google.

Obviously, some people might copy the AMP-link themselves and post it somewhere, but if you're not much on social media, it's entirely possible that you just haven't seen that yet.

Re: The Problem with AMP

#323

Earlier quoted context omitted.

It just took me 8 clicks and a couple swipes to disable JS in my mobile browser, Chrome on Android. Another 8 clicks and couple swipes to enable JS. Is there a faster way to do that?

I know this isn't really and answer to what you are asking, but... On FF mobile, with the "Toggle Javascript enabled" add-on it takes me 3 clicks to reload a page with JS disabled.

NoScript is also available for Android Firefox: https://noscript.net/nsa/

Re: The Problem with AMP

#324
post #319

Earlier quoted context omitted.

Where did I put a moral judgment on all outsourcing? I put a moral judgement on outsourcing to countries that use slave labor , obviously in the context of using slave labor (which is the subject of the thread I'm replying to). That was entirely clear from my comment, and you deliberately chose to ignore that. I will not apologize or make corrections.

Well, I took your comment charitably and addressed the point about individual companies employing abhorrent practices (whether it be labor or otherwise). Obviously, we're not in favor of that. But your claim seems to be that an entire technological sector spanning multiple countries employs slave labor? Its hard to take you seriously at this point.

Again, I never claimed anything that you're saying I claimed. You're taking my comment charitably? Hardly.

My claim is that many companies use (what amounts to) slave labor and that there are financial incentives and economic structures designed around this. It's hard to compete without it, since your competitors are going to be using it. As one example, take entry level programmers on an H1B visa making less than their American counterparts, living with three other H1B roommates in a two-bedroom apartment, sharing one car, working 80 hours a week, knowing that if they get fired they get deported. Or Chinese workers unable to quit but working such horrid conditions that they kill themselves to get out of having to work. Or children in Africa making clothes to sell at Walmart in Illinois.

But again, that's just exactly what I said originally. I literally cannot make my opinion any more clear, so if you're still confused the only thing I can conclude is that you're deliberately misunderstanding in order to provoke an argument, something that is far too common on HN. I don't care if you take me seriously. I care as much about your opinion as you seem to care about mine.

Re: The Problem with AMP

#326
post #129

Earlier quoted context omitted.

Why would clicking the x on a header lead anyone to believe that the entire page ('tab') would be closed? That's not how... any other page element works. The first time I encountered an AMP page I figured clicking the x would load the actual page. I was wrong.

Because x means close/cancel. Looking at chrome right now there are several x's on screen, they will close the tab or the whole browser.

Except this is a mobile only feature, and you never see an x on the page otself to close the page on mobile.

Re: The Problem with AMP

#327

Earlier quoted context omitted.

Why would clicking the x on a header lead anyone to believe that the entire page ('tab') would be closed? That's not how... any other page element works. The first time I encountered an AMP page I figured clicking the x would load the actual page. I was wrong.

Tech people think, x means get me out of this experience. Regular people think close this "pop up" displaying where I clicked to cause this "pop up" to appear.

Well either way that wouldn't result in closing the page.

Re: The Problem with AMP

#328
post #205

I am always confused by this topic. Having browsed the web via mobile for several years with chrome, I have yet to encounter an AMP page. Do I have to enable something or is this region specific? I live in Norway if that matters. Six months ago I switched my mobile browser from chrome to firefox but I still se nothing (nor the bar with the X everyone are talking about).

Sometimes you see Google search results (mostly news) that have a little grey lightning icon underneath the title. When you click the link, the page loads and looks normal, but is actually loaded from the Google AMP cache and the address begins with `google.com/amp`.

Re: The Problem with AMP

#329
post #105
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 actually find AMP an excellent user experience reading articles on mobile internet connections in India. Thr pages load snappily and are very responsive. The ads are not distracting etc. Among news articles, if there's AMP option, I always prefer to click it vs. others.

I agree, and I live in the US. I couldn't care less about seeing the original URL and have never run into a broken page.

Re: The Problem with AMP

#330

Google is abusing its powers. The search rank is our currency and Google has pushed AMP sites to the top for some while. So, everybody is now building weird AMP layers for their sites. We went from a free to a proprietary mobile web in just a few weeks. And we can't do anything. It feels like the times when the Internet Explorer tried to rule except that more people were complaining. The open solution to a faster mob…

The crazy thing is that AMP is open source and this is still happening. I've been tracking their GitHub and what is happening is that while yes, the source is open, they won't let you add anything they don't like. Oh, and if you try to fork AMP you fail the official validators and suddenly your site isn't AMP anymore. What is happening in this case is that open source is doing nothing to stop AMP from being proprieta…

Do you have a specific example of a rejected pull request or feature? It seems also possible that people outside google aren't contributing for other reasons, like lack of interest.
Post reply on HN