Earlier quoted context omitted.
Yeah, I'm tired of not being able to load Reddit from Google SERPs on my phone. Really tired of it. Time to give DuckDuckGo another try I guess...
Have you checked your content blockers?
The Problem with AMP
181–190 of 353 posts
Re: The Problem with AMP
#182It'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.
Yes and the problem is Facebook. Google is fighting FB. In many respects I like gardens, I like curated contents. But I like the web more. The web needs diversity. We need more search engines for instance.
Re: The Problem with AMP
#183I don't like AMP, and I very glad there is now some push back against Google's implementation of it. Fast pages are great, but I suppose I'm missing the background on why it was necessary to do this, when anybody who can implement AMP could presumably have implemented "lightweight non bloated pages" without using it. It's bad enough that I've had to switch to using Bing on mobile, despite the worse results, and I'm a…
Yeah, I'm tired of not being able to load Reddit from Google SERPs on my phone. Really tired of it. Time to give DuckDuckGo another try I guess...
Re: The Problem with AMP
#184Earlier quoted context omitted.
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)
For me, on iOS, I've _never_ had a Reddit AMP page actually finish loading / rendering. Broken since the start
Re: The Problem with AMP
#185Ugh, why does nobody ever point out that AMP and Google displaying AMP are 2 different things? Yes, Google is a huge sponsor in the AMP world but they aren't the only ones involved. AMP itself isn't so bad- asynchronous Javascript (not no script as the article suggests) and it is still valid HTML- it just has extra properties on tags (just how Angular does).
AMP is cancer. I go to a search engine to find content, not your URL-obscuring crappy implementation that I can't even readily share without opening up the URL and dissecting what I originally wanted from it. It's 2017, my phone has a decent quad core and 1080p screen... I don't need your gimped "mobile" version and I don't want you locking me into your platform every time I try and make a search. It's absolutely baf…
Re: The Problem with AMP
#186I wrote a similar(although not as concise) article about 3 month ago: https://www.alexkras.com/google-may-be-stealing-your-mobile-... After which I was invited to meet Google AMP team and to express my concerns, you can read my Q&A here: https://www.alexkras.com/i-had-lunch-with-google-amp-team/ TLDR; A lot of concerns are getting addressed 1. Minor, but the bar at the top is now scrollable on all devices, including…
I hate those bars that reappear when I scroll up, I scroll up to reread a paragraph that I realized I just skimmed or I didn't quite comprehend and instead I get a big blank space with a link to somewhere I do not want to go. They fundamentally break expected scrolling behaviour.
AMP is cancer and should be roundly decried. It's disgusting you can't even turn it off in google search.
They're breaking the web and breaking everyone's web pages and content makers are meekly supporting them instead of kicking up a stink.
Re: The Problem with AMP
#187I really prefer Google and still use it when I'm on my desktop, but I find myself using Bing more and more when I'm on my phone just to avoid AMP. If Google made an easy way to jump from the AMP page to the original page then I wouldn't mind it so much. The # 1 reason why AMP bothers me is when I want to share a link with someone, I don't want to send an AMP link.
AMP doesn't work on firefox.
Re: The Problem with AMP
#188Earlier quoted context omitted.
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.
And websites should honor the "Request desktop version" at all time. It's frustrating when you enable the option and it still bring up the mobile version.
Re: The Problem with AMP
#189Earlier 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, "…
i am curious about the numbers, though i do not know internally or externally if there are numbers showing this. As a power android user, i kind of like the rss-reader-esque look and feel of the amp links. It also opens blazing fast. With these in mind, minor inconveniences (like the address bar) are probably something i wouldn't mind.
Of course you wouldn't mind, since, as you've said elsewhere that you work at Google.
"It is difficult to get a man to understand something, when his salary depends upon his not understanding it!" — Upton Sinclair
Re: The Problem with AMP
#190Earlier quoted context omitted.
Yes and the problem is Facebook. Google is fighting FB. In many respects I like gardens, I like curated contents. But I like the web more. The web needs diversity. We need more search engines for instance.
G+ wasn't enough for them to realize that imitation is not a good strategy to use against FB