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 TazeTSchnitzel on Saturday May 20, 2017 @05:04PM (#14384338)
> I don't mind the idea of having a more standardised subset web page

We already had this two decades ago: WAP, its contemporaries (i-mode), and its immediate successors (XHTML Mobile Profile).

[ Parent | on HN ]
Re:Kill Google AMP before it kills the web by matthewmacleod on Saturday May 20, 2017 @05:12PM (#14384379)
Sure, and those were good solutions for the time - nothing wrong with similar approaches in a modern context.
[ Parent | on HN ]
Re:Kill Google AMP before it kills the web by cramforce on Saturday May 20, 2017 @07:42PM (#14384978)
Big difference was that these had custom renderers. AMP renders in any web browser since they are just web pages.
[ Parent | on HN ]
Re:Kill Google AMP before it kills the web by frozenport on Saturday May 20, 2017 @05:06PM (#14384342)
Except mobile Web adoption in 2002 was poor because of form factor, among other things.
[ Parent | on HN ]
Re:Kill Google AMP before it kills the web by TazeTSchnitzel on Saturday May 20, 2017 @05:07PM (#14384354)
Oh sure. Though I'm not actually trying to criticise the idea of a subset, if anything I'd support it. I'm just pointing to potentially useful precedent. It's not a new idea.
[ Parent | on HN ]