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
31
What else you may like…
Videos
Podcasts
Posts
Articles
Will Voting Machines Get Hacked? Almost Certainly.

Huge number of targets, high value, & many exploits makes voting related hacking a certainty.

00:28:10
November 02, 2024
Apple Removes Ability to Run Unsigned Apps in macOS 15.1

Big Tech's war against "sideloading" continues. With Microsoft and Google not far behind.

The article:
https://lunduke.locals.com/post/6304352/apple-removes-ability-to-run-unsigned-apps-in-macos-15-1

00:23:36
October 31, 2024
Wayback Machine & Google Website Cache Go Offline Weeks Before 2024 Election

With a Presidential election days away, the biggest ways to record online statements are conspicuously broken.

00:13:05
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
Quick Note for all Lifetime Subscribers to The Lunduke Journal.

If you are a Lifetime Subscriber, and you ever encounter any issues with accessing any part of The Lunduke Journal — simply send me an email (Bryan at Lunduke.com). I can usually fix up any account issues in a jiffy.

If you are unsure if your Lifetime Subscription is setup properly, a good way to test is to go to:

https://lunduke.locals.com/content

If you can see the articles and videos on the Content view, you’ve got full access.

For those that picked up a Lifetime Sub last month, you may have received an email from Locals letting you know your subscription was running out. You can safely ignore that. It is a side effect of how Locals processes One-Time payments (all One-Time payments / donations get a single month of access added to the Locals account). If you have a Lifetime Subscription, your Locals account will continue to have full access to all of the content and all of the community features. For life.

If you ever do have any account issues with your Lifetime ...

Wooo! Lunduke is gettin’ some hate E-Mail tonight! Seems like I done gone and poked the right hornets nest!

56 minutes ago

Good news everyone!
Spoiler: they changed the definition of UNIX.

post photo preview
November 03, 2024
post photo preview
Last week at The Lunduke Journal (Oct 20 - Nov 2, 2024)
Linux v. Russia! Internet Archive Weirdness! RISC OS Web Browsing!

Ok, first off: I totally forgot to publish a "week in review" article last week.  Woops.  My bad.  So this article covers the last two weeks.

Second: Over the last 14 days, apparently there's been 16 shows.  Hot dang.

And the news has been all over the map!  The big story, obviously, was the "Linux v. Russia" craziness.  The really wild part of that story is that it's still ramping up.  The next month is going to see some wild stories relating to open source software and sanctions compliance.

Oh!  Oh!  And the Internet Archive stuff!  Insane!

But, you know what my absolute favorite news story was for the last two weeks?  The one about RISC OS having WiFi and a modern web browser now.  That story just made me happy.  It's nice to know that, even when various software companies and organizations are losing their darned minds... there's still bright spots of nerdy joy out there.

The Shows

The Articles

Read full Article
November 02, 2024
post photo preview
Apple Removes Ability to Run Unsigned Apps in macOS 15.1
Big Tech's war against "sideloading" continues.

On Monday, October 28th, Apple released the macOS 15.1 update.  And, with that update, Apple has ratcheted up their war on "sideloading" by completely disabling the ability to run unsigned macOS software.

And signing software, of course, requires an Apple Developer Connection subscription.  Which, for most people, is a costly thing.

 

Every Few Months, A Little Less Freedom

 

Just a little over one month ago (September of 2024), the initial release of macOS 15.0 brought with it a new round of restrictions on running non-signed (also called "non-notarized") applications.  With 15.0, users could still run non-signed software... but they needed to jump through a few extra hoops by openning the System Settings and manually enabling each application they wanted to run.

 

 

This change made running unsigned software on macOS a bit more annoying -- additional steps to do something that used to be a simple "double click on the darned icon" process.  Annoying, to be sure.  But, luckily, all software could still be run.

That all changed -- less than 45 days later -- as Apple released the 15.1 update to macOS, which included the removal of the "Click around in System Settings" option to allow unsigned apps to run.

Now, in 15.1, when you attempt to run a non-notarized piece of Mac software, you will be greeted by a simple error message: "The application 'Finder' does not have permission to open '(null)'."

 

 

No option to run the software whatsoever.  Effectively banning all non-signed software (such as those developed by a hobbyist).

 

The War on Sideloading Continues

 

This isn't exactly a surprising move by Apple.  Over the last few years, all of the Big Tech operating system companies (Microsoft, Apple, and Google) have pushed -- with increasing intensity -- to lock down what software users are allowed to run on their computers.

Increasingly restrictive "application signing" systems, and the removal of "features" which allowed non-signed applications to run, have been a stated goal of all three corporations.

All in the name of a war on, what Big Tech has termed, "Sideloading".

What is "Sideloading", you ask?

"Sideloading" is most simply defined as "The act of installing software on a real computer."  And Apple, Google, & Microsoft are determined to stop people from doing that.

 

 

These companies haven't exactly been quiet about their goal to stop people from installing software on their computers (outside of approved, heavily restrictive mechanisms).  Back in 2021, Apple published a whitepaper entitled "Building a Trusted Ecosystem for Millions of Apps - A threat analysis of sideloading".

 

 

That's right.  Apple considers you having the freedom to install whatever software you want on the computer you own -- something every real computer (including those made by Apple) have done since the dawn of Personal Computing -- to be a "threat".

With macOS 15.1, Apple is taking significant steps to neutralize that "threat".

No software freedom for you.

 

The Last Workaround

 

As of now -- with macOS 15.1 -- there remains one final way to work around these draconian and artificial restrictions.

To do so requires the complete disabling of "Gatekeeper", the system which verifies downloads and restricts the running of non-signed applications.

This can be done via a fairly simple terminal command run as root:

 

sudo spctl --master-disable

 

However, it should be noted that with Apple's ever increasing requirements of application "notarization" -- and increasing reliance on the Mac App Store for software distribution (which ties into Gatekeeper) -- the full disabling of "Gatekeeper" seems likely to cause issues going forward with "Apple approved" methods of installing software.

Likewise, at Apple's current rate of attacks against "sideloading", the ability to turn off Gatekeeper may not be long for this world at all.

 

Don't Laugh, Google & Microsoft Users

 

While the news, today, is focused on Apple (their fight against the most basic freedoms of computing -- the ability to run software)... both Microsoft and Google have made it clear that they are all in on the war against sideloading.

Case in point: Google is migrating Android software away from "APK" application packages... to the far more restrictive "AAB" application bundles.  Microsoft, likewise, is pushing for a reliance on their online store.

So users of Android, ChromeOS, & Windows shouldn't laugh.  You're next.

Users of a variety of open source, alternative operating systems (such as Linux, BSDs, and many others), however, can laugh all they want.

Read full Article
November 02, 2024
post photo preview
Funny Programming Pictures Part LXII
Number 7 will SHOCK you!

No Ctrl-C's were harmed in the making of this post.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

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