From: Dave Horsfall <dave@horsfall.org>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Does anybody know the etymology of the term "word" as in collection of bits?
Date: Sat, 10 Sep 2022 07:44:57 +1000 (EST) [thread overview]
Message-ID: <alpine.BSF.2.21.9999.2209100734520.71191@aneurin.horsfall.org> (raw)
In-Reply-To: <C2BED78B-3E59-429E-B4A3-FB2ED0E2B577@iitbombay.org>
On Fri, 9 Sep 2022, Bakul Shah wrote:
> And yet according to Wilner's article "the B1700 appears to require less
> than half the memory needed by byte-oriented systems to represent
> programs. Comparisons with word-oriented systems are even more
> favorable."
The Burroughs series were beautiful machines; the hardware ran native
ALGOL (and thus were perfect); my favourite "B" still remains the B1500.
Things went downhill after the unholy alliance betwixt M$ and Inhell...
> Figure 9 shows sample sizes for Cobol, Fortran and RPG II programs
> comparing B1700 code sizes with other systems. I was surprised to
> see this but didn't look further.
COBOL? FORTRAN? RPG? Those are all swear words to me :-)
-- Dave
next prev parent reply other threads:[~2022-09-09 21:45 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-09 19:39 Nelson H. F. Beebe
2022-09-09 20:27 ` Bakul Shah
2022-09-09 21:12 ` Henry Bent
2022-09-09 21:44 ` Dave Horsfall [this message]
2022-09-10 1:49 ` [TUHS] Obscene languages (was: Does anybody know the etymology of the term "word" as in collection of bits?) Greg 'groggy' Lehey
-- strict thread matches above, loose matches on Subject: below --
2022-09-11 13:30 [TUHS] Re: Does anybody know the etymology of the term "word" as in collection of bits? Douglas McIlroy
2022-09-11 15:08 ` John Cowan
2022-09-11 15:30 ` Bakul Shah
2022-09-11 15:45 ` Paul Winalski
2022-09-11 16:20 ` Steve Nickolas
2022-09-09 18:46 Norman Wilson
2022-09-10 1:35 ` Paul Winalski
2022-09-09 17:26 Douglas McIlroy
2022-09-09 1:33 Douglas McIlroy
2022-09-09 2:12 ` Larry McVoy
2022-09-13 14:23 ` John Foust via TUHS
2022-09-09 2:45 ` George Michaelson
2022-09-16 5:55 ` Marc Donner
2022-09-08 21:16 Noel Chiappa
2022-09-08 21:24 ` Dan Halbert
2022-09-08 18:20 Noel Chiappa
2022-09-08 19:28 ` Jim Capp
2022-09-08 16:51 [TUHS] " Jon Steinhart
2022-09-08 16:56 ` [TUHS] " Andrew Hume
2022-09-08 17:28 ` Dan Halbert
2022-09-09 0:00 ` Greg 'groggy' Lehey
2022-09-09 15:49 ` Paul Winalski
2022-09-09 18:44 ` Bakul Shah
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=alpine.BSF.2.21.9999.2209100734520.71191@aneurin.horsfall.org \
--to=dave@horsfall.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).