The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: "John P. Linderman" <jpl.jpl@gmail.com>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: Does anybody know the etymology of the term "word" as in collection of bits
Date: Thu, 8 Sep 2022 15:22:27 -0400	[thread overview]
Message-ID: <CAC0cEp99yedHwgQOEF+OHX3j+8+RgBQWQTPSLmc06tA=fJkL=g@mail.gmail.com> (raw)
In-Reply-To: <20220908180149.CB4DC18C077@mercury.lcs.mit.edu>

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

In Brailsford's youtube series in Computerphile (something I came across
through BWK's interview with Brailsford),
Episode 86
<https://www.youtube.com/watch?v=ixJCo0cyAuA&list=PLUTypj9XuPp4YBaHucPvr-zisHwfEGIEq&index=87>
is
about "Where Did Bytes Come From?".  He claims that if you wanted to do
decimal arithmetic on a
binary machine, you'd want to have 10 digits of accuracy to capture the 10
digit log tables that were then popular.
10 digits is around 33 to 36 bits, so words ended up that size (or half
that size), 36 or 18 bits. (Brailsford's lectures are
fabulous, by the way, likely to appeal to TUHS types.)

I like that explanation better than the story I heard that the IBM 709
series had 36 bit words because Arthur Samuel,
then at IBM, needed 32 bits to identify the playable squares on a
checkerboard, plus some bits for color and kinged
(if that's the proper term for getting across the board and gaining the
ability to move toward either side). Samuel was
famous for writing a checker playing program that played champion-quality
checkers.

On Thu, Sep 8, 2022 at 2:02 PM Noel Chiappa <jnc@mercury.lcs.mit.edu> wrote:

>     > On Sep 8, 2022, at 9:51 AM, Jon Steinhart <jon@fourwinds.com> wrote:
>
>     > One of those questions for which there is no search engine
> incantation.
>
> Whatever it is, it's really old. I found it used, not quite in the modern
> sense, in "Hi-Speed Computing Devices", by ERA, 1950. It was used, in the
> modern sense, in "Planning a Computer System", Buchholz,1962.
>
>         Noel
>

[-- Attachment #2: Type: text/html, Size: 2566 bytes --]

      reply	other threads:[~2022-09-08 19:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-08 18:01 Noel Chiappa
2022-09-08 19:22 ` John P. Linderman [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='CAC0cEp99yedHwgQOEF+OHX3j+8+RgBQWQTPSLmc06tA=fJkL=g@mail.gmail.com' \
    --to=jpl.jpl@gmail.com \
    --cc=jnc@mercury.lcs.mit.edu \
    --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).