From: Clem Cole <clemc@ccc.com>
To: Lars Brinkhoff <lars@nocrew.org>
Cc: TUHS <tuhs@tuhs.org>
Subject: [TUHS] Re: "9 skills our grandkids won't have" - Is this a TUHS topic?
Date: Fri, 1 Jul 2022 14:09:51 -0400 [thread overview]
Message-ID: <CAC20D2P423hnYvP_17_PC=Z1is8Y2d7=BzbgsTkQgrHJC2zmAw@mail.gmail.com> (raw)
In-Reply-To: <7wv8sg6dd2.fsf@junk.nocrew.org>
[-- Attachment #1: Type: text/plain, Size: 552 bytes --]
On Fri, Jul 1, 2022 at 11:50 AM Lars Brinkhoff <lars@nocrew.org> wrote:
> I believe CP/M was inspired by many of the DEC traditions,
>
If you do some Internet searching, there is an interview (IIRC from Byte
Magazine in the late 1970s) where its author (Gary Kildall) straight out
said he was trying to emulate RT-11 for an 8080. The funny thing to
remember is that Kildall was a language guy, he wrote CP/M to demo his
programming language PL/M for Intel. The demo ended up having more
longevity than the tool he was trying to sell.
ᐧ
[-- Attachment #2: Type: text/html, Size: 1563 bytes --]
next prev parent reply other threads:[~2022-07-01 18:11 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-01 13:31 Nelson H. F. Beebe
2022-07-01 14:02 ` Steve Nickolas
2022-07-01 15:01 ` Clem Cole
2022-07-01 19:22 ` Phil Budne
2022-07-01 19:53 ` Clem Cole
2022-07-02 19:36 ` Leah Neukirchen
2022-07-02 19:50 ` Clem Cole
2022-07-03 0:22 ` John P. Linderman
2022-07-01 15:50 ` Lars Brinkhoff
2022-07-01 16:20 ` Warner Losh
2022-07-01 18:18 ` Clem Cole
2022-07-01 18:09 ` Clem Cole [this message]
2022-07-01 18:45 ` Steve Nickolas
-- strict thread matches above, loose matches on Subject: below --
2022-06-30 13:14 [TUHS] " steve jenkin
2022-06-30 13:39 ` [TUHS] " Marc Donner
2022-06-30 13:54 ` Tom Teixeira
2022-06-30 14:08 ` Marshall Conover
2022-06-30 14:15 ` Larry McVoy
2022-06-30 14:32 ` Will Senn
2022-06-30 14:42 ` Pierre DAVID
2022-06-30 15:44 ` Larry McVoy
2022-06-30 15:23 ` Clem Cole
2022-06-30 15:35 ` Clem Cole
2022-06-30 14:23 ` Michael Kjörling
2022-06-30 15:12 ` Al Kossow
2022-06-30 15:55 ` Adam Thornton
2022-06-30 16:37 ` Paul Winalski
2022-07-01 13:05 ` Ori Idan
[not found] ` <Yr7zs59NtbXcRCu4@mbsks.franken.de>
2022-07-01 13:17 ` Matthias Bruestle
2022-07-01 13:36 ` Angus Robinson
2022-07-01 13:58 ` Marc Donner
2022-07-01 14:05 ` Henry Bent
2022-07-01 14:37 ` Marc Donner
2022-07-01 14:41 ` Blake McBride
2022-09-16 17:04 ` Michael Parson
2022-07-02 23:01 ` Mark Sutton
2022-07-03 0:08 ` John Cowan
2022-06-30 19:24 ` Michael Huff
2022-06-30 19:56 ` Jon Steinhart
2022-06-30 20:43 ` Robert Stanford via TUHS
2022-06-30 20:49 ` Chris Pinnock via TUHS
2022-06-30 21:11 ` ron minnich
2022-06-30 21:21 ` Larry McVoy
2022-06-30 21:24 ` Marc Donner
2022-06-30 21:41 ` James Johnston
2022-06-30 21:54 ` Larry McVoy
2022-06-30 22:05 ` Dr Iain Maoileoin
2022-06-30 22:18 ` Rik Schneider
2022-06-30 22:51 ` Marc Donner
2022-07-01 10:48 ` Tom Ivar Helbekkmo via TUHS
2022-06-30 21:24 ` Chris Pinnock via TUHS
2022-07-01 0:41 ` Tomasz Rola
2022-07-01 0:46 ` Larry McVoy
2022-07-01 1:13 ` Larry Stewart
2022-07-01 18:12 ` Harald Arnesen
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='CAC20D2P423hnYvP_17_PC=Z1is8Y2d7=BzbgsTkQgrHJC2zmAw@mail.gmail.com' \
--to=clemc@ccc.com \
--cc=lars@nocrew.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).