And All That HTML5 Malarkey

There was a period when “HTML5” appeared on conference slides, job postings, and — memorably — a shiny orange badge you were encouraged to paste on your homepage. Much of it was malarkey: the term got stretched to cover CSS3, JavaScript APIs, WebSockets, and roughly anything invented after 2008. Let us do the unglamorous work of separating signal from noise.

The noise

A good deal of what was sold as HTML5 was never HTML at all:

• Rounded corners, shadows, gradients, transitions. That is CSS. Real progress, wrong label.
• Geolocation, WebSockets, Web Workers, WebGL. These are JavaScript APIs living alongside HTML, not markup.
• “HTML5 apps will kill native.” A prophecy repeated for a decade with mixed results at best.
• The version badge. A logo is not a capability. Wearing it proved nothing about your code.

None of this was bad technology. The malarkey was the packaging — a single buzzword doing the work of an entire platform, which left everyone vaguely confident and precisely uninformed.

The genuine wins

Underneath the froth, the actual HTML additions were solid and have aged well:

1. A specified parser. Error handling written down so browsers agree on the DOM — arguably the single most valuable change.
2. Semantic sectioning. <article>, <nav>, <main>, and friends, giving structure to machines.
3. Native media. <video> and <audio> with captions, ending the plugin era.
4. Better forms. New input types and built-in validation.
5. The living standard model. Continuous evolution instead of frozen versions.

A quick smell test

When someone calls a feature “HTML5,” ask where it actually lives. If you can write it as a tag or attribute in a document, it is HTML:

<video controls src="talk.mp4"></video>  <!-- HTML -->
<input type="email" required>             <!-- HTML -->

navigator.geolocation.getCurrentPosition() // JS API
.card { border-radius: 12px; }             /* CSS */

The word “HTML5” is a useful umbrella and a terrible spec. Reach for it in conversation; never reach for it when you actually need to know what a feature is.

Why the pedantry pays

Precision is not snobbery here — it is debuggable knowledge. If you know that your rounded corners are CSS and your offline behavior is a service worker, you know where to look when either breaks. “HTML5” as a catch-all tells you nothing about the failure in front of you. Keep the enthusiasm; drop the umbrella term the moment real work begins.