News for hackers. Stuff that matters.

A comment on Kill Google AMP before it kills the web. Parent comment

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.

[ Parent | on HN ]
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'.
[ Parent | on HN ]
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.
[ Parent | on HN ]
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.
[ Parent | on HN ]