From: Adam Thornton <athornton@gmail.com>
To: Douglas McIlroy <douglas.mcilroy@dartmouth.edu>,
The Eunuchs Hysterical Society <tuhs@tuhs.org>,
Computer Old Farts Followers <coff@tuhs.org>
Subject: Re: [COFF] [TUHS] Book Recommendation
Date: Sun, 5 Dec 2021 21:25:11 -0700 [thread overview]
Message-ID: <CAP2nic1Vu4Wq-Ptqcat7CthdAYRmWXzidARSk_mNbjXQMvxLQQ@mail.gmail.com> (raw)
In-Reply-To: <CAKH6PiWtxq7vwh_WdVtZx9-qqN5aNr+t14eTAJx9-eLWjYF0BQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 857 bytes --]
Probably time to move this to COFF, but
along the line of Fission for Program Comprehension....
I wonder how many of you don't know about Don Lancaster.
Pioneer in home computing back when that meant something, inventor of a
very low cost 1970s video terminal (the TV Typewriter), tremendously
skilled hacker, brilliant guy.
Also still alive, lives a couple hours away from me in Safford, AZ, and has
been doing fantastic research on Native American hanging canals for the
last couple decades.
Anyway: he wrote a magnificent piece on how to understand a (6502) program
from its disassembly, which reminded me of Gibbons's work:
https://www.tinaja.com/ebooks/tearing_rework.pdf
I don't think Don ever had a lot of crossover with the more academic world
of Unix people, but he's one of my heroes and I have learned a hell of a
lot from his works.
Adam
[-- Attachment #1.2: Type: text/html, Size: 1155 bytes --]
[-- Attachment #2: Type: text/plain, Size: 141 bytes --]
_______________________________________________
COFF mailing list
COFF@minnie.tuhs.org
https://minnie.tuhs.org/cgi-bin/mailman/listinfo/coff
next parent reply other threads:[~2021-12-06 4:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAKH6PiWtxq7vwh_WdVtZx9-qqN5aNr+t14eTAJx9-eLWjYF0BQ@mail.gmail.com>
2021-12-06 4:25 ` Adam Thornton [this message]
2021-12-06 14:11 ` Clem Cole
2021-12-06 14:22 ` Dan Cross
2021-12-06 14:29 Noel Chiappa
[not found] <CAKH6PiU59OwWNC3so20muvECi+2HKaX2PRAizjLjjO1J=Vwgug@mail.gmail.com>
[not found] ` <20211116040858.se3ygq2butxqopcx@localhost.localdomain>
[not found] ` <CAC20D2Phn_VahO7A2MCEHgMRV7isVo9W3s6wqdvw6Q=0koE9jg@mail.gmail.com>
[not found] ` <CAFH29tq3J2=dUEufiUApMgWBAFogYfj-nWL5C2WD950xW59_4A@mail.gmail.com>
[not found] ` <CAP2nic0d7Kg1-i3w=6220NfBTQh7TaZ6nMsNx7NWLE+dTn5Z7w@mail.gmail.com>
2021-11-16 16:19 ` Clem Cole
[not found] <CAKH6PiXtVetBZbyvOiWZFSTvNebSTEuaYkOoUx4KPg4wtdvN8g@mail.gmail.com>
[not found] ` <CAFH29tomxKDFn-pRBT21-X+m4ugzzn-tuGyY-Cq0hN6i5-=oeQ@mail.gmail.com>
2021-11-16 15:53 ` Adam Thornton
[not found] ` <b355e6b8-720d-3078-d54a-2beb5ff79bd4@mhorton.net>
[not found] ` <CAEdTPBdVnPQMaDX0jOL81EkL1M7Eg=U4qWPwKMsr6SBc2Zz9vw@mail.gmail.com>
2021-11-23 15:23 ` Clem Cole
2021-11-23 19:40 ` Dan Cross
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=CAP2nic1Vu4Wq-Ptqcat7CthdAYRmWXzidARSk_mNbjXQMvxLQQ@mail.gmail.com \
--to=athornton@gmail.com \
--cc=coff@tuhs.org \
--cc=douglas.mcilroy@dartmouth.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).