Computer Old Farts Forum
 help / color / mirror / Atom feed
From: Adam Thornton <>
To: Larry McVoy <>, COFF <>
Subject: [COFF] Re: [TUHS] Porting the SysIII kernel: boot, config & device drivers
Date: Sun, 1 Jan 2023 10:21:38 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

> On Dec 31, 2022, at 6:40 PM, Larry McVoy <> wrote:
> All true except for the Forth choice.  It's as bad, maybe worse, as 
> choosing Tcl for your language.  I've written a ton of Tcl but I
> need the Tk GUI part so I put up with Tcl to get it.  I'd never 
> push Tcl as a language that other people had to use.  Same thing
> with Forth.
> I dunno what I'd pick, Perl in the old days, Python now (not that
> I care for Python but everyone can program it).  Just pick something
> that is trivial for someone to pick up.

(Moved to COFF) 

I rather like FORTH.  Its chief virtues are that it is both tiny and extensible.  It was developed as a telescope control language, as I recall, and in highly constrained environments gives you a great deal of expressivity for a teeny tiny bit of interpreter code.  I adored my HP 28S and still do: that was Peak Calculator, and its UI is basically a FORTH interpreter (which also, of course, functions just fine as an RPN calculator if you don't want to bother with flow control constructs).

But I also make the slightly more controversial claim that FORTH is just LISP stood up on end.

These days I think the right choice for those sorts of applications would be Micropython.  Yes, a full-on Python interpreter is heavyweight, but Micropython gives you a lot of functionality in (comparatively) little space.  It runs fine on a $4 Pi Pico, for instance, which has IIRC 256KB RAM.

And if you find yourself missing TCL, there's always Powershell, which is like what would happen if bash and TCL had a really ugly baby that just wouldn't shut up.  The amazing thing is that access to all the system DLLs makes it *almost* worth putting up with Powershell.


       reply	other threads:[~2023-01-01 17:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
     [not found] ` <>
     [not found]   ` <>
     [not found]     ` <>
     [not found]       ` <>
     [not found]         ` <>
     [not found]           ` <>
     [not found]             ` <>
     [not found]               ` <>
2023-01-01 17:21                 ` Adam Thornton [this message]
2023-01-01 17:33                   ` Lars Brinkhoff
     [not found]       ` <>
     [not found]         ` <>
     [not found]           ` <20230101212609.yjg2poiggil7pwat@illithid>
2023-01-02  9:37             ` [COFF] " Ralph Corderoy

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).