5 ms·
As a user, I really like AMP. It converts terrible web experiences into non-terrible ones because it forcibly removes the rope for major websites to hang themse
by vorpalhex 8y ago
As a user, I really like AMP. It converts terrible web experiences into non-terrible ones because it forcibly removes the rope for major websites to hang themselves with.
As a developer, most of my concerns with AMP are with it being very Google centric and controlled - and the addition of Cloudflare didn't really solve those for me. Seeing AMP move to a TSC however does, and I really hope that it helps AMP become a globally adopted standard instead of a "Google thing".
- chrischen 8y agoI hate AMP as a user. It breaks iOS Safari reader mode, and i always have to do extra work to get the actual link to the page. I'm also on LTE, so there's not really any noticeable speed difference on mobile. Initially there were also rendering bugs making 50% of amp clicks result in blank pages for me.
- vorpalhex 8y agoIt's not delivery speed that I care about, it's "time to first paint". I want to read the damned news article, not wait for your crappy fonts to load and have to mute your autoplaying video nonsense.
- baxtr 8y agoExactly the same for me. It starts wir subtle things: Why do they have to override the system scroll speed? Then, as you point out, I’m a heavy user of safaris read mode which is essentially solving for the same problem as AMP. For me, the best thing about amp is the link leading to the non amp version EDIT: I have to apologize for both of my points. The scrolling thing was fixed as somebody pointed out and the reading mode works just fine for most pages I just checked. Have tried to avoid AMP for a long time I guess...
- sincerely 8y agoI heavily use my browsers' reader modes as well but isn't the idea that if you load the regular page then use the reader mode you end up downloading more data than you would have if you just visited an AMP page? From a user's perspective (absent ideological concerns about the implications of AMP in its current implementation) the latter is preferable to me.
- saagarjha 8y agoThe scroll speed issue has been fixed on later versions of iOS.
- ktosobcy 8y agoThe problem with AMP is... it forces JS just to push less data and focus on content while the solution would be... to simply use less junk on the website. IMHO this could be done with limiting what is allowed on the website.
- mattmanser 8y agoI think the (much, much) bigger problem with AMP is that it restricts the future. If you're only allowed a subset of HTML otherwise your site won't rank which is entirely dictated by how fast you can get back to Google serving more ads, bye-bye HTML, bye-bye innovation, bye-bye open web. When all websites have to be AMP as you get heavily penalised for not being AMP, why would you keep up the HTML version of your site? The internet will be forced by Google onto a standard that heavily benefits google, and heavily penalises the things we should actually care about, which is an open web on our own servers, not controlled by centralized CDNs, and content makers. What's worse, how long before google start including "other people searched for" in their top bar as soon as you scroll up a bit? And then how long before google start showing their adverts at the top of your web page?