Saved
Web & cloud

HTML

1989

HTML is not a programming language — it is a contract between author and browser about what text means, not how it looks.

Worth your time?4.5/5Yes.Study the whole thing.What works, what does not, who it is for ↓
8:50in productionCh. 1 · Semantics, not styling/ 8:50 · ceiling 15 min
4 chapters · 8:50Ceiling 15:00

The brief is written and checked. The video joins this page when it is cut.4 chapters · 1 min read · 8:50 planned

Read the brief

HTML (1989) is a markup language built from angle-bracketed elements, conceived as an SGML application, first publicly described in late 1991, and standardised as HTML 2.0 in 1995. It provides structural semantics for text — headings, paragraphs, lists, links, quotes — and serves as the foundational grammar for browser-based document composition.

Chapters & takeaways4
  1. 0:45
    Semantics, not styling

    HTML defines meaning, not appearance — it tells browsers what content is, not how to draw it.

  2. 2:04
    SGML in disguise

    Angle brackets and SGML make HTML both human-readable and machine-parsable — but only if you accept SGML’s constraints.

  3. 3:57
    Elements are non-negotiable

    Every HTML page is a tree of nested elements — no exceptions, no shortcuts, no defaults beyond the DTD.

  4. 5:47
    Browser contract, not language

    Browsers do exactly one thing with HTML: interpret tags to compose pages — nothing more, nothing less.

1 more chapterFewer chapters
Worth your time?

Yes. Study the whole thing.

4.5/ 5
What works
  • defines structural semantics reliably
  • enables consistent browser interpretation
  • supports extensible, SGML-based syntax
What does not
  • render styling
  • execute logic
  • manage state
  • enforce validation beyond SGML parsing
Study it if
  • web authors needing structured, interoperable document markup
Skip it if
  • developers needing interactivity or dynamic behaviour
Who should study it, and who should skipHide who it is for
The written brief1 min read

What it is and the problem it solves

HTML is a markup language that web browsers use to interpret and compose text, images, and other material into visible or audible web pages. It solves the problem of inconsistent, non-interoperable hypertext formatting on early networks.

How it works

HTML uses angle-bracketed tags to define structural semantics — headings, paragraphs, lists, links, quotes — for plain text. It is an application of SGML, with syntax formally defined by an SGML DTD in the IETF’s 1993 Internet Draft.

What works

HTML elements serve as the building blocks of HTML pages. They denote structural semantics reliably. Browsers parse them consistently. The SGML foundation ensures syntactic rigour and extensibility.

What does not

HTML does not render presentation. It does not execute logic. It does not manage state. It does not define behaviour. It does not enforce validation beyond SGML parsing rules.

What it changes

It replaces proprietary document formats with a shared, tag-based grammar for hypertext composition — enabling interoperable, browser-driven rendering across networks.

Is it worth your time

Yes — if you need to structure document content for browser interpretation. No — if you require styling, interactivity, or data handling. It does one thing well and nothing else.

Same field · Web & cloud4 of 17
8:22
HTTPTim Berners-Lee · 1989HTTP is the minimal, functional core that made the Web possible — not because it was elegant, but because it was small, implementable, and free.
11:30
NCSA MosaicMarc Andreessen · 1993NCSA Mosaic (1993) was the first browser to display images inline with text, submit forms, and explore collaborative annotation. Developed at NCSA by Marc Andreessen and Eric Bina, it launched in January 1993 as alpha/beta 0.5, reached version 1.0 in April, and shipped to Windows, Mac, and Amiga by October. Its blue/purple link convention and cross-platform ports catalysed explosive growth—from 50 to 10,000 websites and from 1% to 25% of internet users within a year. Collaborative annotation remained unshipped. It established the visual and functional grammar of the web—but offered no security model, no dynamic updating, and no scripting.
9:41
Google Chrome2008Chrome is not a browser that evolved—it is a delivery mechanism for Google’s ecosystem. It succeeded by embedding itself where users already were: Android, search, and cloud services. Its technical innovations (V8, multi-process, Blink) enabled scale—but its real function is alignment: between Google’s services, device platforms, and developer expectations. It trades openness for predictability, and performance for control.
8:40
JSONDouglas Crockford · 2001JSON is a syntactic constraint, not a data model. It works because it refuses to be more than a wire format — and fails wherever meaning, safety, or evolution is required.
Up next in Technology

Hughes Network Systems

1971 · 10:57

VSAT built the first scalable satellite internet — then froze in geosynchronous orbit while the world moved to low Earth orbit.

10:57