Kill Google AMP before it kills the web

Post by PrimHelios » Mon, May 22, 2017, 5:04 AM UTC

MBCook wrote: post #261

PrimHelios wrote: post #248

Earlier quoted context omitted.

> You deployed something that worked horribly on iOS Except that thing was a bug in Safari. They used perfectly valid plain HTML without any hacks or JS.

It wasn't a bug in Safari, that was simply the way the scrolling behavior was implemented in iframes. It was still there choice to deploy using iframes knowing that that was the way it felt. They could've use JavaScript to load the contents into a div or simply pushed so far users to a page that had nothing but the AMP content on it. They left it severely sub optimal and decided that was good enough… making google si…

Post by quadrupleslap » Mon, May 22, 2017, 7:28 AM UTC

danso wrote: post #71

MBCook wrote: post #54

Earlier quoted context omitted.

If that's all Google truly cared about they could've simply put a heavy penalty on Pages that rendered slow or presented garbage. Instead they invented their own thing which caused you to stay on Google sites using Google services to read other peoples content… and said they did it to speed things up. It feels like that was either justification after the fact or that was with the original engineer had in mind but was…

> If that's all Google truly cared about they could've simply put a heavy penalty on Pages that rendered slow or presented garbage. There already is a penalty for slow-loading pages, but you make a good point that the penalty could be increased to the point where publishers would be forced to adapt accordingly. However, outside of the news ecosystem, that would end up penalizing a much larger base of content creators…

Post by [deleted] » Mon, May 22, 2017, 7:48 AM UTC

bikamonki wrote: post #347

AMP was born dead no need to kill it. As the webmaster of many websites, the last time I heard customers complain about rankings in SRPs was ten years ago. Their main concern nowadays is likes, follows and shares. I keep telling them: put some effort on your website, own your audience, you do not own your FB page much less the fans and likes there. They don't listen. Trapped in the hype. In this light, how do I sell…

Post by qb45 » Mon, May 22, 2017, 8:46 AM UTC

Houshalter wrote: post #451

qb45 wrote: post #437

Earlier quoted context omitted.

There are extensions which add buttons to quickly enable/disable JS on per-site basis like NoScript for Firefox. Also, Firefox reader view fixes many websites which otherwise render empty with JS disabled for reasons I didn't bother investigating.

I don't think it's possible to get browser extensions on an old iOS device.

Post by ddalex » Mon, May 22, 2017, 11:53 AM UTC

ejcx wrote: post #279

ghughes wrote: post #272

Earlier quoted context omitted.

It turns out that if you strip most of the JS bloat from a webpage and serve it from a fast CDN, the page loads way faster. Shocking stuff.

It's not shocking but AMP enforces it. People talk a lot of trash about AMP, but until there's another solution that allows me to go to a news website and actually read it, I'm an AMP supporter.