Tag Archives: HTML


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 digitalstart.net 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.

ACCU, W3C, W3Schools or W3Fools?

One of my favourite sites is ACCU. They claim

ACCU is an organisation of programmers who care about professionalism in programming and are dedicated to raising the standard of programming.

W3C sets the standard on HTML, XML tagging and CSS styling etc. Now there is a new sheriff or boy in town, W3Fools that announce themself as

W3Schools an intervention.

Below, we take a deeper look at some (you can look up the rest for yourself) of the persons that claim to be members of the Front-end Dev Community. It is unclear to me whether that is the Finnish site Frontend.fi – The Developer Community. It was not easy to find a link, and I did not takt the time to Google them. Time is also a limiting production factor for me. The remaining time of my life is too short to Google newcomers too often.

Here are some of the members (that have a site or mention a company that have a site) in alphabetical after twitter ID:

  • @addyosmani: addyosmani
  • @ajpiano: ajpiano
  • @antimatter15 antimatter15
  • @ard

    Adventurer & treasure hunter in a land of JavaScript, HTML5 and NodeJS. Web game developer & 1/2 designer at Crytek.


We stop there. Our impression is that most of them have their WordPress powered blog sites. The last site is bad. It takes time to load. It took more than a minute the first time I clicked the link.

We find some value on the front page. This


$sql="INSERT INTO Persons (FirstName, LastName, Age)

Yikes. This code exposes an application to trivial SQL injection attacks and should never have been posted. It contravenes every best practice.

is an important objection. Today this is trivially avoided by using the php PDO object and prepared statements. PDO set restrictions that most web developers never need do know anything about. But I am unaware of whether the people at W3Schools as well as the people at W3Fools know about object relational mapping, PDO and prepared statements in php 5.3 and higher. Should they join forces and go back to school? Some of them may find it worth the effort to start on OoopSchool.com where we have collected a lot of resources.

Today there are much talk about standards. The statement on the home page about the Opera Web Standards Curriculum is nothing new to the author of this post. Read more on the following interesting WebProWorld thread about:

Bing, Google and Yahoo! Join Forces with schema.org

You may also find some value in this WPW thread about the easiest programming language where assembly 🙂 is also mentioned.

Don’t look at my sites. Hopefully they deliver content that is seen in most browsers. Some of them are old and this blog is WordPress powered. In my personal view:

Content is still King and refactoring to better code and markup is still Queen.