From: "Michael Kjörling" <e5655f30a07f@ewoof.net>
To: coff@tuhs.org
Cc: tuhs@tuhs.org
Subject: [COFF] Re: (TUHS -> COFF?) [TUHS] Re: Clever code
Date: Wed, 14 Dec 2022 12:08:21 +0000 [thread overview]
Message-ID: <a721dc6d-702a-4f37-8cf3-265e219f0d7d@home.arpa> (raw)
In-Reply-To: <xon1qp2yzdv.fsf@anduin.eldar.org>
On 14 Dec 2022 06:54 -0500, from brad@anduin.eldar.org (Brad Spencer):
> [...] but you needed to know 6809 or 68000 assembly to create anything
> new for the OS itself,
Wasn't that the norm at the time, though? As I recall one of the
things that really set UNIX apart from other operating systems up
until about the early 1990s was precisely how machine-independent it
was by virtue of (with the exception of the early versions) having
been written in something other than assembler.
--
✍ Michael Kjörling 🏡 https://michael.kjorling.se
“Remember when, on the Internet, nobody cared that you were a dog?”
parent reply other threads:[~2022-12-14 12:08 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <xon1qp2yzdv.fsf@anduin.eldar.org>]
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=a721dc6d-702a-4f37-8cf3-265e219f0d7d@home.arpa \
--to=e5655f30a07f@ewoof.net \
--cc=coff@tuhs.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).