The problem of AMP HTML
Link: Get AMP’d: Here’s what publishers need to know about Google’s new plan to speed up your website
Now, AMP essentially asks you to build a parallel-universe version of your site that strips out not just anything that’s slow, but anything that might be slow.
AMP tries to do something maybe even more significant: change the way that the web is built, killing off some technologies and advantaging others. In a world of controlled platforms and walled app gardens, the web is the last open space standing, built over two decades, and there’s something irksome about a few Google engineers deciding which parts to ban.
The sample AMP pages on display this morning look a lot like the web of, say, 2002, shrunk down to a phone screen. Like an IE 5.5 emulator.
I think the problem with AMP HTML is that breaks a web page content into two sets. Each article needs to have a normal page and an AMP version.
Why can’t google just extract the content of the article and display it? A reading friendly extraction like Safari readev view, Pocket, Readability.
And if any one think the web today is boring, the AMP move just makes the web pages much more boring because it cuts all the interactive things.
Published on 2015-10-12 by Makzan.
More articles like this:
-
Highlighted
-
Web Technologies
Previous ← A simple comparison between AsciiDoc and Markdown
Next → Corpus—A collection of CSS