Lunduke
News • Science & Tech
The story of the first "computer bug"... is a pile of lies.
A fun, endearing, delightful pile of lies.
August 28, 2023
post photo preview

Many of us have heard the story of “The First Computer Bug”. It goes something like this…

On September 9, 1947 — at 3:45pm — Grace Hopper recorded the “first actual case of a bug being found” in her logbook. The bug was a moth found between the relay contacts of the Harvard Mark II computer.

The story is a fantastic one. A bug. An actual bug causing a computer to misbehave.

The fact that this was found by Grace Hopper — who is an absolute legend in the world of computer programming — adds to the legendary status of this story. And this story has been repeated countless times as the origin for why we use the term “bug” when talking about errors and defects in computer software.

Here is a picture of the actual log book page. Note that the moth in question is actually taped onto the page. Which, I must say, is a pretty awesome way to handle a “bug report.”

Photo of the log book from 1947.

So that you can get a full appreciation for the computer we’re talking about here, this is what the console of the Harvard Mark II computer looked like. Note the teletypes to either side of the desk

The Console of the Harvard Mark II. Image courtesy of Gwen Bell.

See that cool control sitting in the middle of the table? Here’s a close up view of that beauty. Just because.

Photo courtesy Smithsonian.

And what about those relays where that moth was found? Well. Here is a picture of the bank of relays of the Harvard Mark II. This is where the moth was discovered.

Photo courtesy Smithsonian.

Petty cool right?

And a cool story! The origin of the “computer bug”! By Grace Hopper! Awesome!

A story so cool that it has been repeated (with ever so slight variations) in so many major publications. Everything from the New York Times to Newsweek has repeated this anecdote. Telling this story in computer publications is almost a sacred tradition at this point. Such as in the January, 1984 edition of BYTE (which has a truly fantastic magazine cover).

 

Note this retelling of the story references the Harvard Mark I instead of the Mark II. Technically both machines existed at this time. But it was likely the Mark II.

There’s just two problems with this story:

  1. This was not the origin of term “bug” being used for engineering — including computer software.

  2. And it was not likely discovered — or recorded — by Grace Hopper.

Seriously.

The two most critical parts of this story — a story repeated more times than almost any other throughout the computing world — are not true. At all.

Let’s start with the logbook.

The likelihood is… that this logbook was not actually Grace Hopper’s. The handwriting does not match Hopper’s — even the National Museum of American History considers this logbook page to not be written by Hopper. And the discovery of the moth in the relay was not Hopper’s discovery either.

Who wrote this logbook entry? That remains a bit of a mystery. One that I would very much like to solve. Considering the relatively small size of the team who worked on the Mark II, I’m hopeful to eventually get a definitive answer to this.

Now. Let’s address the other factual problem with this story…

This is not the first time that computer defects were referred to as “bugs”.

In fact, that was already common at this point — as it had become standard throughout many engineering fields for several decades.

In fact, here is a quote from Thomas Edison — dated March 3rd, 1878 — where he talks about finding a bug affecting his technology:

“You were partly correct, I did find a ‘bug’ in my apparatus, but it was not in the telephone proper. It was of the genus ‘callbellum.’ The insect appears to find conditions for its existence in all call apparatus of telephones” - Edison

Here is a scan of the entire letter from Edison:

In fact, even this is not the first time Edison, himself, used “bug” to talk about engineering defects.

A “bug” was a common issue in Quadruplex Telegraphs in the 1800s — specifically referring to “false signals”. In order to fix these “bugs”, Edison invented something called a “Bug Trap”. Which led to a series of trademark disputes well into the 1920s.

And, by this time, “bug” was quickly becoming a common term for any sort of engineering error or anomaly. As computer creation progressed during the 1940s, the terminology was both well understood and used by those early computer engineers and programmers.

Whoever wrote that famous 1947 log entry — “first actual case of a bug being found” — was making a joke. It was, indeed, the first time a physical, insect “bug” was recorded to be found inside a computer.

  • It was not, however, the first time a joke was made about finding a real “bug” in a work of engineering (that would go to Edison).

  • Nor was it the first time that a computer glitch would have been referred to as a “bug”.

  • Nor was it found or recorded by Grace Hopper.

This has become one of those stories which has been repeated so often — and blindly accepted as fact (in large part, I think, because we have a picture of the actual moth) — that it will continue to be be re-told, over and over again, and never questioned.

Even though it’s filled with falsehoods.

Still. A fun story, though.

community logo
Join the Lunduke Community
To read more articles like this, sign up and join my community today
7
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

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

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

post photo preview

I see there have been new faces contributing to the discourse here. Welcome to you and those who like to observe on the sidelines. I hope you find informational and entertaining.

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