From: Douglas McIlroy <firstname.lastname@example.org>
To: TUHS main list <email@example.com>
Subject: [TUHS] Re: Managers/architects (was: AIX moved into maintainance mode)
Date: Thu, 19 Jan 2023 16:30:42 -0500 [thread overview]
Message-ID: <CAKH6PiVB3mLE-Wi3yYigrbrvSDmrGhuKLxtujAEPh_D9ELmAQg@mail.gmail.com> (raw)
> My guess is that Ivan Sutherland probably qualified back when he still
> programmed ... I mean, after all, he invented the linked list in order to
> implement his thesis program (Sketchpad) in about 1960.
I don't know whether Sutherland invented the linked list, but if he
did, it had to be before he worked on sketchpad. I attended a lecture
about Lisp in 1959 in which McCarthy credited list-processing to
IPL-V, whose roots Newell places in 1954. Sketchpad ran on TX 0, which
became operational in 1956.
My nomination for a triple-threat computer guy is Vic Vyssotsky. A
great programmer, he invented the first stream-processing language
(BLODI) and bitwise-parallel dataflow analysis. As an architect, he
invented the single underlying address space for multics. As a
manager, he oversaw the building of and later ran the lab that became
AT&T Research. Finally he founded the DEC Cambridge Lab. He was a
subtle diplomat, too, who more than once engineered reversals of
policy without ruffling feathers.
Relative to linked lists, I remember Vic perceptively touting the then
startling usage J=NEXT(J).in Fortran.
next reply other threads:[~2023-01-19 21:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 21:30 Douglas McIlroy [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-01-19 17:50 [TUHS] " Noel Chiappa
2023-01-19 18:00 ` [TUHS] " Marc Donner
2023-01-19 18:09 ` Charles H Sauer (he/him)
2023-01-20 3:47 ` John Cowan
2023-01-19 21:12 ` Lawrence Stewart
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).