The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Greg 'groggy' Lehey <grog@lemis.com>
To: John Cowan <cowan@ccil.org>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Bug etymology (was: 70th anniversary of (official) programming errors)
Date: Wed, 16 Jun 2021 11:06:30 +1000	[thread overview]
Message-ID: <20210616010630.GK23809@eureka.lemis.com> (raw)
In-Reply-To: <CAD2gp_T3_1k5Q05VB2p5Cjjcm-mnW6XbTuoC=8WxHmn=96_rdw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1720 bytes --]

On Tuesday, 15 June 2021 at 18:54:47 -0400, John Cowan wrote:
> On Tue, Jun 15, 2021 at 6:25 PM Steffen Nurpmeso <steffen@sdaoden.eu> wrote:
>> As not being hard-to-the-core i may have missed it, but also in
>> 1951, in March, the wonderful Grace Hopper "conceives the first
>> compiler, called A-O and later released as Math-Matic.  Hopper is
>> also credited with coining the term 'bug' following an incident
>> involving a moth and a Mark II.
>
> Yes, but wrongly.  The label next to the moth is "First actual case of bug
> being found", and the word "actual" shows that the slang term already
> existed then.

Correct.  The Oxford English Dictionary has two overlapping
definitions (along with dozens of others).  In each case I've shown
the earliest attestation:

 5. Originally U.S.

  a. A defect or fault in a machine (esp. an electrical or electronic
     one), or in a process, etc.

     1875 Operator 15 Aug. 5/1 The biggest ‘bug’ yet has been
          discovered in the U.S. Hotel Electric Annunciator.

  b. Computing. An error or other cause of malfunction in a computer
     program, piece of software, etc.

     1952 Rev. Electronic Digital Computers
          (Amer. Inst. Electr. Engineers) 18/2 The week we spent in
          getting the last bug out of our instruction program was an
          investment we hated to have to make.

It's interesting that they differentiate between the two.

Greg
--
Sent from my desktop computer.
Finger grog@lemis.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA.php

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 163 bytes --]

      parent reply	other threads:[~2021-06-16  1:15 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-15 22:16 [TUHS] 70th anniversary of (official) programming errors Steffen Nurpmeso
2021-06-15 22:54 ` John Cowan
2021-06-15 23:44   ` Dan Cross
2021-06-16  3:48     ` Rob Pike
2021-06-16  4:13       ` Bakul Shah
2021-06-16 21:57         ` Steffen Nurpmeso
2021-06-18 20:19           ` John Cowan
2021-06-18 21:00             ` Steffen Nurpmeso
2021-06-18 22:59               ` Steffen Nurpmeso
2021-06-19 13:34               ` Harald Arnesen
2021-06-19 13:39                 ` Niklas Karlsson
2021-06-19  7:57             ` [TUHS] Bugs, Bööge and Bogeymen (was: 70th anniversary of (official) programming errors) Greg 'groggy' Lehey
2021-06-19 15:48               ` Steffen Nurpmeso
2021-06-19 15:52                 ` Niklas Karlsson
2021-06-19 16:36                   ` Steffen Nurpmeso
2021-06-19 21:05                 ` Harald Arnesen
2021-06-20  3:30                   ` arnold
2021-06-16  1:06   ` Greg 'groggy' Lehey [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210616010630.GK23809@eureka.lemis.com \
    --to=grog@lemis.com \
    --cc=cowan@ccil.org \
    --cc=tuhs@tuhs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).