Accelerated mobile pages (AMP) and HTML amp (HTML ⚡)

On february 24 2016, Google and Twitter’s accelerated mobile page (AMP) project was officially launced with the motto An architectural framework built for speed. You can read more about HTML AMP or HTML ⚡ on more precisely in the section with the heading Advice for webmasters, especially those who want to set up a new site. By following the links on that site, you find everything you need to know about AMP, AMP HTML, AMP JS and more.

What about HTML or HTML5?

It is relevant to remind the reader of what the Web Hypertext Application Technology Working Group (WHATWG) write about HTML and HTML5, the history of HTML and the future of HTML. All the quotes below are taken from the introduction to WHATWG’s HTML Living Standard.  Sorry for the long cite, but I think it is necessary.

The term “HTML5” is widely used as a buzzword to refer to modern Web technologies, many of which (though by no means all) are developed at the WHATWG.

The idea that HTML’s evolution should be reopened was tested at a W3C workshop in 2004, where some of the principles that underlie the HTML5 work (described below), as well as the aforementioned early draft proposal covering just forms-related features, were presented to the W3C jointly by Mozilla and Opera. The proposal was rejected on the grounds that the proposal conflicted with the previously chosen direction for the Web’s evolution; the W3C staff and membership voted to continue developing XML-based replacements instead.

Shortly thereafter, Apple, Mozilla, and Opera jointly announced their intent to continue working on the effort under the umbrella of a new venue called the WHATWG. A public mailing list was created, and the draft was moved to the WHATWG site. The copyright was subsequently amended to be jointly owned by all three vendors, and to allow reuse of the specification.

For a number of years, both groups then worked together. In 2011, however, the groups came to the conclusion that they had different goals: the W3C wanted to publish a “finished” version of “HTML5”, while the WHATWG wanted to continue working on a Living Standard for HTML, continuously maintaining the specification rather than freezing it in a state with known problems, and adding new features as needed to evolve the platform.


Now in addition to  W3C and WHATWG, there is a third group, the AMP project, that will develop a third HTML standard. So will this standard be developed independent of WHATWG’s living standard, will it be implemented as a subset or will WHATWG implement its own accelerated (core) version? Only time will tell.