News for hackers. Stuff that matters.
Re:Kill Google AMP before it kills the web by EvilTerran on Saturday May 20, 2017 @06:05PM (#14384604)
Seems to me the right approach would be for sites to embrace the HTML5 semantic tags (<nav>, <article> and so forth), and browsers to offer a way to view just that semantically-marked-up content - without scripts, with restricted CSS, and maybe with some kind of filtering out of third-party content. Something like Firefox's "reader view", but including more bits of the page.

So the browser would still be downloading the exact same HTML document (straight from the publisher's server, how you want it) - just then ignoring all the clutter. Compare to AMP, which AFAICT necessitates serving a whole separate version of the page with only the blessed markup... it reminds me of the bad old days, having a separate mobile site instead of a single responsive design for all devices. All seems rather antithetical to that grand ideal of separating structure and presentation.

Re:Kill Google AMP before it kills the web by captainmuon on Saturday May 20, 2017 @10:59PM (#14385481)
An idea I've been floating for a while is to have two HTML profiles in the future. Call it HTML6 document and HTML6 app.

HTML6 document is a restricted subset, similar to what you suggest. I would still allow complete design flexibility, and I might even allow a subset of JS, but only for presentation purposes. Definitely not turing complete, and no ajax etc.. Probably I wouldn't allow cross-origin resources with credentials. So you could include an image or stylesheet, but the browser would not send along cookies. What I'm aiming for is a replacement for PDF, something you could read on an ebook, etc.. Just a plain document.

On the other hand, I'd have HTML6 app to be able to use the complete web platform.

Re:Kill Google AMP before it kills the web by madeofpalk on Sunday May 21, 2017 @03:41AM (#14386180)
This sounds good as a dream, but in reality it would actually achieve anything because everyone, including the publishers, would just use 'HTML6 app'.
Re:Kill Google AMP before it kills the web by codedokode on Sunday May 21, 2017 @03:44AM (#14386188)
You can make light web pages with current technologies but nobody wants a page without advertisement, popups, analytics and notifications.
Re:Kill Google AMP before it kills the web by swift on Sunday May 21, 2017 @02:33PM (#14388469)
HTML6 document is essentially epub, which is HTML and CSS under the hood.
Re:Kill Google AMP before it kills the web by Vinnl on Sunday May 21, 2017 @06:08AM (#14386560)
Isn't that pretty much what AMP is? IIRC, you don't need a separate version of the page with only AMP on it - Google's cache just extracts only the AMP parts of your page when caching. Or has this changed since I saw it? (And if so, why - that would probably also be an argument against your solution :) )