Lunduke
News • Science & Tech
Myth: "HTML was invented by Tim Berners-Lee"
The truth? He copied someone else's work.
April 10, 2024
post photo preview

Go to any search engine and type in, "Who invented HTML" and you'll -- almost always -- be given the following answer (or some variation on it):

"HTML was invented by Tim Berners-Lee."

Want to know a little secret?  That is utter hogwash.

"Heresy," you proclaim!  "Everyone knows Sir Tim Berners-Lee, who was knighted by the Queen and won of the Turing Award, created the HyperText Markup Language!  You better have some serious proof to backup such an outlandish claim!"

Challenge accepted.

To start with, let's look at a simple HTML document.

HTML.  I think?  Maybe?

Oh, wait.  Hold up.  I accidentally used the wrong screenshot.  That's not HTML... that's SGML.  A totally different language used several years before HTML.

Here.  Let me post an HTML screenshot.

Or is it the other way around?

Dagnabbit!  I did it again!  This time I accidentally posted a picture showing an HTML sample next to an SGML sample!

Funny.  They look exactly the same.

What the heck is SGML?

SGML -- the Standard Generalized Markup Language (aka ISO 8879) -- was set as a standard back in 1986... 7 years before the release of the HTML 1.0 specification.

Over in Switzerland, at CERN ("Conseil européen pour la Recherche nucléaire" aka "European Organization for Nuclear Research"), Anders Berglund adopted SGML primarily for usage in formatting documentation.

Title page of the CERN SGML User's Guide

That variation on SGML -- dubbed "SGMLguid" -- remained in usage at CERN for several years.  And, in 1987, Tim Berners-Lee was hired as a contractor at CERN.

Where, wouldn't you know it, part of Tim's job was using that CERN implementation of SGML.

A few years later, HTML was born.  Just to jog your memory, here is a document marked up in both Tim's HTML 1.0... and the CERN variant of SGML.

Mic drop.

Find the difference.  I dare ya.

Now, I'm not saying that Sir Tim Berners-Lee directly copied HTML from SGML (and the implementation that Anders Berglund made of it)... wait... yes.  Yes, I am.  I am saying exactly that.

HTML is a copy.

That's not entirely fair to Sir Tim.

In defense of Sir Tim, Knight of Her Majesty the Queen, he did do more than simply make a copy of SGML when "creating" HTML.

In fact, Sir Tim made three -- very important -- changes to SGML in order to make it HTML:

  1. He added the "a href" link tag.
  2. He changed the file extension from ".sgml" to ".html".
  3. He implemented an SGML parser which only implemented a little over a dozen tags from SGML... and ignored the rest.  And called it "HTML".

While item 1 (the HREF tag) is a noteworth change over SGML, items 2 and 3 (which are very real) only serve to reinforce the fact that HTML is -- for the most part -- simply a copy of an existing SGML implementation.  And a less functional one at that.

As an example, here is the very first HTML document ever written.  Which, other than the usge of HREF, is identical to SGML.

The very first HTML document, written by Sir Tim Berners-Lee - December 3rd, 1990

Change that "href" tag to something which SGML recognizes -- such as a different "Anchor" type (which is what the "a" stands for in "a href") -- and this instantly becomes a valid SGML document.

But... HyperText!  That's important!

While the addition of a standardized way of including simple looking HyperText Anchors (aka "links" or "a href") was a welcome addition to SGML... that was, at the time, the only significant change which Sir Tim implemented in his SGML copy known as HTML.

(Other than changing the file extension to ".html", of course.  That was pretty... important.  *cough*)

Back in the late 1980s, people were adding HyperText (and linking between "documents") everywhere.  Shoot.  Apple already had a fully graphical HyperText system known as HyperCard.

HyperCard 1.0

In fact, nearly every major On-Line service of the day included some form of linking between documents.

With the HyperText hype train fully underway -- across the entire computing universe -- it was only natural that any update to -- or copy of -- SGML would include that functionality.

So... yes.  Sir Tim Berners-Lee adding "HREF" to SGML was important.  But, otherwise, HTML was little more than a direct copy of existing work.

None of this is disputed.

These are historical facts that are well documented.  Shoot.  The W3C, itself, agrees with everything I said above.

So why, then, is this important to talk about any of this?

Because the getting history right is important.

The ridiculous myth that "Tim Beners-Lee invented HTML" has been repeated, over and over again, every single day... for decades... resulting in that myth becoming accepted as gospel truth.  With awards and acclaim (and even a knighthood) showered upon Sir Tim, in part, because of that myth.

The work which Tim Berners-Lee did on that initial HTML 1.0 release was -- to put it bluntly -- trivial.  At most.  Bordering on plagiarization.

The reality is... Tim stood on the backs of giants.  He wasn't simply inspired by others... he directly copied them.  To the point where Tim's work is almost indistinguishable (see the screenshots above) from the work which he copied (and is almost always attributed to him).

Some of the giants he stood on the backs of:

  • Anders Berglund (and his work on SGMLguid at CERN).
  • Charles Goldfarb, Edward Mosher and Raymond Lorie (the original creators of GML, upon which SGML was based -- note that "GML" was named after the first letters in their last names).
  • Ted Nelson and Douglas Engelbart for their early (1960s) work on HyperText systems.
  • And so many others.

Every single one of those names contributed something new and significant to the world of HyperText and Markup Languages.  They blazed new trails.

Sir Tim copied the existing SGML, changed the file extension, removed a few features, added an anchor tag (which was a feature everyone and their dog was doing at the time), and released it.

"Modifying a Work" vs "Claiming it as Your Own"

If I were to, for example, fork the Linux kernel -- change one line of code -- and release it as "NotLinuxWinkWink"... I can do that.  It's an open source project, and I can legally make modifications and release copies.

But, if I were to then receive near universal acclaim for inventing "NotLinuxWinkWink"... that's a problem.  Legality aside, that just wouldn't be right.  Or true.

Likewise, if I were to copy the specification for the C programming language... and change one line (or add one feature)... it would not be true to say that I "invented" a new language.  I tweaked something that already existed (that somebody else built).  A little.

Thus is the case with Sir Tim and HTML.

Was Sir Tim an instrumental figure in computing?  You bet.  Does he deserve a mention in the history books because of that?  Absolutely.  And in some positive ways, at that!

But did he "invent" HTML?  Not by a long shot.

And we need to stop repeating that myth.

community logo
Join the Lunduke Community
To read more articles like this, sign up and join my community today
32
What else you may like…
Videos
Podcasts
Posts
Articles
The Case for 486 Support in Linux (And Everywhere Else)

Linux is dropping support for 486 CPU's. Heck, I'm still upset about losing support for the 386. We should bring it back. Let me explain why.

More from The Lunduke Journal:
https://lunduke.com/

00:15:23
Rust Coreutil Re-Write Dev Says Project "So Subpar I Don't Even Have Words"

The developers of Rust UUtils, which is now shipping in Ubuntu by default, have realized re-writing battle tested code "full of edge cases" is actually hard.

More from The Lunduke Journal:
https://lunduke.com/

00:17:21
If Memory Safety is The Goal Rust is Not The Solution

Every significant Rust program (GNU Coreutils re-write, System76's Cosmic Desktop, etc.) is filled with "unsafe" code. If being Memory Safe was truly important, Rust is a terrible solution.

More from The Lunduke Journal:
https://lunduke.com/

00:30:14
November 22, 2023
The futility of Ad-Blockers

Ads are filling the entirety of the Web -- websites, podcasts, YouTube videos, etc. -- at an increasing rate. Prices for those ad placements are plummeting. Consumers are desperate to use ad-blockers to make the web palatable. Google (and others) are desperate to break and block ad-blockers. All of which results in... more ads and lower pay for creators.

It's a fascinatingly annoying cycle. And there's only one viable way out of it.

Looking for the Podcast RSS feed or other links? Check here:
https://lunduke.locals.com/post/4619051/lunduke-journal-link-central-tm

Give the gift of The Lunduke Journal:
https://lunduke.locals.com/post/4898317/give-the-gift-of-the-lunduke-journal

The futility of Ad-Blockers
November 21, 2023
openSUSE says "No Lunduke allowed!"

Those in power with openSUSE make it clear they will not allow me anywhere near anything related to the openSUSE project. Ever. For any reason.

Well, that settles that, then! Guess I won't be contributing to openSUSE! 🤣

Looking for the Podcast RSS feed or other links?
https://lunduke.locals.com/post/4619051/lunduke-journal-link-central-tm

Give the gift of The Lunduke Journal:
https://lunduke.locals.com/post/4898317/give-the-gift-of-the-lunduke-journal

openSUSE says "No Lunduke allowed!"
September 13, 2023
"Andreas Kling creator of Serenity OS & Ladybird Web Browser" - Lunduke’s Big Tech Show - September 13th, 2023 - Ep 044

This episode is free for all to enjoy and share.

Be sure to subscribe here at Lunduke.Locals.com to get all shows & articles (including interviews with other amazing nerds).

"Andreas Kling creator of Serenity OS & Ladybird Web Browser" - Lunduke’s Big Tech Show - September 13th, 2023 - Ep 044

Tagged if you use a VPN???

Small is beautiful!!

17 hours ago

Interesting things about Ada and Spark...

One member of the Praxis staff has said: "Our defect rate with Spark is at least 10 times, sometimes 100 times lower than those created with other languages."[4]

I bet Iron Oxide never saw that one coming!!

SPARK, which is based on Ada, offers unparalleled safety and security through its design and support for deductive formal verification. You simply can’t write better code.

Oooohhh...I'd have to see it to believe it!! Them's fighting words for Iron Oxide!!!

Absence of Runtime Errors
Run-Time errors include issues traditionally found by automatic checks at run-time and defensive code, such as out-of-bound array access, division by zero, overflow and more. SPARK proves that no run-time errors are possible in your code.

I seriously do not think that the developers of Iron Oxide saw this blurb, otherwise they would get the Spark!

Memory Safety
Through a combination of mitigation of dynamic memory usage, borrow-checking analysis and advanced ...

Last call for the "Amiga" Lifetime Subscriber Wall. It's almost full!

Holy smokes, that was fast.

The 6th Lunduke Journal Lifetime Subscriber Wall (aka the “Amiga OS 3.1” Wall) was introduced… what… a week ago?

I kid you not, the darn thing is already almost full! I was wildly unprepared for how popular this would be!

There’s enough space left for maybe 5 or 6 more names. Tops. Then I’ve gotta declare “Wall 6 (Amiga) is Full” and start Wall Number 7!

Here’s what all of the Lifetime Subscriber Walls look like (each shown at the end of every Lunduke Journal video):

 

If you want to get onto the Lifetime Subscriber Wall (and have any chance of making it onto the Amiga Wall before it’s full) here’s what you need to do (and do it quickly):

  1. Grab a Lifetime Subscription to The Lunduke Journal (if you don’t already have one).

    1. A Lifetime Sub includes all the standard perks (plus a few) and can be picked up via Locals, Substack, or Bitcoin (whichever you prefer).

  2. Email “bryan at lunduke.com” and let me know how you would like your name displayed (“Joe A.”, “Joseph Arnold”, “JoeyPants”, “SirJJMcManly”, etc.)

It’s first come, first served.

If you’ve already emailed me about being added to the wall, your spot is secured.

For the rest of you: Chop chop. At the current rate, I would be very surprised if the “Amiga Wall” wasn’t full by some time this weekend.

“Lifetime Wall 7” will be unveiled after the final name is added to the Amiga Wall. And, yes, it will be a different (awesome) retro computing platform.

As always, a huge thank you to every subscriber to The Lunduke Journal. Absolutely none of this would be possible without your support.

-Lunduke

Read full Article
post photo preview
Amiga Lifetime Wall & March Lunduke Journal Stats!

Hello all of you amazing Lunduke Journal subscribers!

With March now behind us, I wanted to give you crazy kids a quick “behind the scenes” look at the stats for The Lunduke Journal. Because Inside Baseball stuff is fun.

The Amiga Wall!

But before we dive into charts and numbers… behold! The brand new 6th Lifetime Subscriber Wall of Shame Awesomeness! The AmigaOS 3.1 Wall!

 

Every Lifetime Subscriber Wall (which I show at the end of each video) is a real screenshot from a different computing platform. Mostly retro. All awesome.

 

If you’d like to see your name listed on the new AmigaOS 3.1 wall, grab a Lifetime Subscription (if you don’t already have one) and toss me an email. I update the walls about once each week with new names.

The last few Lifetime Walls filled up incredibly quickly. So if the Amiga Wall interests you, I wouldn’t wait too long. Hint, hint.

March 2026 Stats

The big news: Total “views” were way, way up in March.

A fair bit beyond what was anticipated. A hair over 19 million during the month.

 

That’s in total, across all platforms. As usual, the audio podcast and X lead the way in terms of total views/listens for shows (by quite a lot).

Interestingly, we saw significant “views” growth on even the smallest platforms in March (Facebook and TikTok).

Free subscribers also took a major jump in March, with the largest one month gains ever (I’m pretty sure, certainly the largest this year or last). Up 7,623 over the month before.

 

Again, new subscribers grew across the board. The biggest gains were seen on X, but all platforms saw a significant bump.

Hard to complain about that!

The top 3 shows for March were all focused on the Age Verification laws:

While those were the top 3… it’s worth noting that the top 10 (and, really, the top 15 or so) shows for the month were all incredibly close in terms of viewership numbers.

As always, a huge thank you to all of The Lunduke Journal subscribers. You make all of this possible.

-Lunduke

Read full Article
Lifetime Wall Number 6, Plus How to Access MP4s & Forum

A few quick reminders for all of you amazing Lunduke Journal subscribers:

First: If you have any kind of payed subscription (Monthly, Yearly, or Lifetime) there are a bunch of cool perks available to you. MP4 Downloads, PDF eBooks, and access to the Lunduke Journal Forum. All the details on how to gain access to everything is right here.

Enjoy.

Second: At the end of this next week I’ll be unveiling “Lifetime Subscriber Wall of Shame” number Six at the end of all new Lunduke Journal videos.

 

At that same time I will be updating and permanently locking down Walls 1 through 5.

If you are already a Lifetime Subscriber, and would like to be added to the new Wall number 6 (or to one of the couple remaining spots on Walls 4 and 5), email me (bryan at lunduke.com) with how you would like your name to be displayed (full name, first name only, nick name… any way you like).

  1. CRT Linux Pico Wall: Full

  2. DOS Word Wall: Full

  3. Win 3.11 Notepad Wall: Full

  4. MacOS 9 Wall: 2 Spots Left

  5. PalmOS Wall: 1 Spot Left

  6. Mystery Wall: Open

Those final spots on the MacOS and PalmOS Walls are first come first served. The first people to request those spots get them.

Everyone else will roll over into Wall 6. Which is a secret, retro computer platform. You’ll dig it.

If you have already contacted me regarding being added to one of these walls (or changing the way your name is displayed), I’ve already got you on the list for the changes later this next week.

If you don’t already have a Lifetime Subscription, grab one and get yourself on the wall.

It’s pretty sweet.

-Lunduke

Read full Article
See More
Available on mobile and TV devices
google store google store app store app store
google store google store app tv store app tv store amazon store amazon store roku store roku store
Powered by Locals