From: Clem Cole <clemc@ccc.com>
To: Dave Horsfall <dave@horsfall.org>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Typing tutors
Date: Mon, 8 Feb 2021 18:01:23 -0500 [thread overview]
Message-ID: <CAC20D2NMGY+c233=1ftca8A7aWgOwWtRtUVWfW55FMjk3sJ-QA@mail.gmail.com> (raw)
In-Reply-To: <alpine.BSF.2.21.9999.2102090900390.70858@aneurin.horsfall.org>
[-- Attachment #1: Type: text/plain, Size: 1196 bytes --]
On Mon, Feb 8, 2021 at 5:21 PM Dave Horsfall <dave@horsfall.org> wrote:
> I know that I'm gonna be outclassed here, but I taught myself BASIC,
> ALGOL, and FORTRAN (ugh! well, it was WATFOR then WATFIV) from my school
> days in the late 60s onwards.
>
Many much older and more experienced than I on this list. I'm a relative
youngster that started in the late 1960s. So Dave, I have to say, ditto,
but I will add a couple of assemblers to the early list (360 BAL, HP2000,
and PDP-8 and 10). My father showed me the GE-635 assembler in
probably 1968, but I never managed to write anything meaningful in it.
>
> COBOL tried to be drilled into me, but I firmly rejected it (but for some
> odd reason I still know it, but deny all knowledge of it).
>
Funny, I dodged COBOL, but not PL/1 and APL. With the latter, I maintained
the York/APL interpreter on TSS for a bit. I also saw a number of
languages on the 10's like SAIL, SNOBOL, and over course BLISS. All before
I saw C on the Fifth Edition of UNIX. As I've said before, when I first
saw it, I was not impressed. Little did I know Dennis and Ken would rot my
brain - (and I'm thankful that they did).
Clem
ᐧ
[-- Attachment #2: Type: text/html, Size: 2740 bytes --]
next prev parent reply other threads:[~2021-02-08 23:02 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-06 2:57 Will Senn
2021-02-06 16:55 ` Clem Cole
2021-02-06 17:22 ` Ron Natalie
2021-02-06 17:29 ` Clem Cole
2021-02-06 17:33 ` Mary Ann Horton
2021-02-06 17:47 ` Ron Natalie
2021-02-06 18:06 ` Clem Cole
2021-02-06 22:38 ` Dave Horsfall
2021-02-06 22:47 ` Niklas Karlsson
2021-02-07 0:25 ` John Cowan
2021-02-08 22:20 ` Dave Horsfall
2021-02-08 22:58 ` David Barto
2021-02-08 23:01 ` Clem Cole [this message]
2021-02-07 17:43 ` Mary Ann Horton
2021-02-07 19:28 ` Dan Cross
2021-02-07 21:32 ` Nemo Nusquam
2021-02-07 23:17 ` Henry Bent
2021-02-07 23:55 ` Steve Nickolas
2021-02-08 0:56 ` Henry Bent
2021-02-08 5:15 ` Erik E. Fair
2021-02-08 5:33 ` Steve Nickolas
2021-02-08 15:54 ` Will Senn
2021-02-08 5:29 ` Doug McIntyre
2021-02-08 20:41 ` Andrew Newman
2021-02-06 18:56 ` David Barto
2021-02-08 21:50 ` Dave Horsfall
2021-02-09 16:29 ` Mary Ann Horton
-- strict thread matches above, loose matches on Subject: below --
2017-04-06 2:15 [TUHS] I just noticed all the cfont aka C++ in research Jason Stevens
2017-04-06 2:20 ` Noel Hunt
2017-04-06 2:21 ` Jason Stevens
2017-04-06 6:57 ` [TUHS] Unix emacs at Bell Labs and elsewhere Erik E. Fair
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='CAC20D2NMGY+c233=1ftca8A7aWgOwWtRtUVWfW55FMjk3sJ-QA@mail.gmail.com' \
--to=clemc@ccc.com \
--cc=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).