From: Alec Muffett <alec.muffett@gmail.com>
To: Larry McVoy <lm@mcvoy.com>
Cc: The Unix Heritage Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Question about BSD disklabel history
Date: Sun, 31 Dec 2023 23:41:44 +0000 [thread overview]
Message-ID: <CAFWeb9Lgb5ekx0TspknUtHwH=PaHG=8e3PXNW13=0Cx21fV4Fw@mail.gmail.com> (raw)
In-Reply-To: <20231231230615.GE19322@mcvoy.com>
[-- Attachment #1: Type: text/plain, Size: 548 bytes --]
On Sun, 31 Dec 2023, 23:25 Larry McVoy, <lm@mcvoy.com> wrote:
> Yeah, I get it, Forth is like some weird lisp
> and the lisp people love lisp.
>
HERESY! Forth is a RPN stack language.
It's closer to Java bytecode in a whole bunch of ways, but its lineage
comes squarely out of embedded systems like radio telescope control. It's a
solid choice.
Funny I was only posting about it earlier today in respective of the recent
iPhone privilege escalation / exploit:
https://alecmuffett.com/article/108789
...which links to some Forth examples.
-a
[-- Attachment #2: Type: text/html, Size: 1393 bytes --]
next prev parent reply other threads:[~2023-12-31 23:42 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-31 17:30 [TUHS] " Grant Taylor via TUHS
2023-12-31 17:38 ` [TUHS] " arnold
2023-12-31 20:07 ` Warner Losh
2024-01-01 0:13 ` Bakul Shah
2023-12-31 20:27 ` Phil Budne
2023-12-31 21:02 ` Warner Losh
2024-01-01 0:26 ` Grant Taylor via TUHS
2024-01-01 2:22 ` Warner Losh
2024-01-01 3:24 ` Grant Taylor via TUHS
2023-12-31 21:31 ` Clem Cole
2023-12-31 22:07 ` Warner Losh
2024-01-01 16:00 ` Clem Cole
2024-01-02 18:49 ` Warner Losh
2024-01-02 19:30 ` Chet Ramey
2024-01-02 20:07 ` Clem Cole
2024-01-02 19:50 ` Dan Cross
2024-01-02 19:55 ` Jim Capp
2024-01-02 20:11 ` Dan Cross
2024-01-02 20:30 ` Dan Cross
2024-01-02 20:50 ` Clem Cole
2024-01-02 21:04 ` Dan Cross
2023-12-31 22:46 ` G. Branden Robinson
2023-12-31 23:06 ` Larry McVoy
2023-12-31 23:37 ` Al Kossow
2023-12-31 23:41 ` Alec Muffett [this message]
2024-01-02 20:48 ` Dan Cross
2024-01-02 21:17 ` John Cowan
2024-01-03 3:33 ` Theodore Ts'o
2024-01-03 3:57 ` Warner Losh
2024-01-03 4:03 ` Warner Losh
2024-01-03 4:30 ` Theodore Ts'o
2024-01-03 5:10 ` Warner Losh
2024-01-03 15:56 ` Dan Cross
2024-01-03 16:37 ` Theodore Ts'o
2024-01-03 16:41 ` Dan Cross
2024-01-04 8:42 ` arnold
2024-01-04 18:26 ` Kevin Bowling
2024-01-03 14:39 ` Dan Cross
2023-12-31 23:08 ` Phil Budne
2023-12-31 23:37 ` G. Branden Robinson
2023-12-31 23:59 ` Warner Losh
2023-12-31 23:50 ` G. Branden Robinson
2024-01-01 0:09 ` Al Kossow
2023-12-31 21:55 Norman Wilson
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='CAFWeb9Lgb5ekx0TspknUtHwH=PaHG=8e3PXNW13=0Cx21fV4Fw@mail.gmail.com' \
--to=alec.muffett@gmail.com \
--cc=lm@mcvoy.com \
--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).