Path: ...!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: rbowman <bowman@montana.com>
Newsgroups: alt.folklore.computers,comp.os.linux.misc
Subject: Re: The joy of FORTH (not)
Date: 23 Oct 2024 23:02:45 GMT
Lines: 33
Message-ID: <lntdklFquoqU1@mid.individual.net>
References: <vdnvk0$49ai$2@dont-email.me> <lmb9k2F64inU8@mid.individual.net>
	<vdqlcs$lo51$1@dont-email.me>
	<TKqcnfnts-lvnJ_6nZ2dnZfqn_WdnZ2d@earthlink.com>
	<pRDMO.80813$7OO5.26774@fx43.iad> <lmh1avF2k8fU1@mid.individual.net>
	<MZScnWkZT7T_Hon6nZ2dnZfqnPWdnZ2d@earthlink.com>
	<vf27ib$9pgg$1@dont-email.me> <ErcRO.309187$v8v2.137739@fx18.iad>
	<vf3t70$itru$9@dont-email.me> <lnlparFlf82U5@mid.individual.net>
	<vf4hrt$pqrl$3@dont-email.me> <lnmbutFodq5U1@mid.individual.net>
	<vf5442$sjo3$1@dont-email.me> <20241021075543.00000494@gmail.com>
	<vf6f0q$13ctc$2@dont-email.me> <20241021151652.00005675@gmail.com>
	<vf6n47$14l9a$3@dont-email.me> <lno9vqF368kU2@mid.individual.net>
	<vf6u3q$15nlq$3@dont-email.me> <20241022095931.00001d38@gmail.com>
	<vf93a5$1l20u$6@dont-email.me>
	<299011000.751331039.035254.peter_flass-yahoo.com@news.eternal-september.org>
	<vf9d06$1mkkd$2@dont-email.me> <20241023080437.00003148@gmail.com>
	<vfbo0f$28v56$4@dont-email.me> <20241023143625.00004792@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Trace: individual.net 0rCF02v/ht9VrC6fGS4jZg0QEkzHlKry4Akl3sfX6o0MoozNFj
Cancel-Lock: sha1:qGyUp5DW3HnuT9vAsM/6CbcBo6Q= sha256:NWVbV4qcdMYXuShZ1XGajfbsXqRwXiB105fgfNBA4XQ=
User-Agent: Pan/0.149 (Bellevue; 4c157ba)
Bytes: 3160

On Wed, 23 Oct 2024 14:36:25 -0700, John Ames wrote:

> On Wed, 23 Oct 2024 20:57:51 -0000 (UTC)
> Lawrence D'Oliveiro <ldo@nz.invalid> wrote:
> 
>> 512kiB seems to be the recommendation for MicroPython. For the 32kiB
>> one, I would want to use a cross-compiler for some more
>> resource-efficient language, like C.
> 
> Which you certainly could do! Or, alternatively, you could embed a more
> resource-efficient but interactive threaded interpreter, like Forth ;)

So far working with C++ and the Pico W has been interesting. Putting the 
board in the BOOTSEL mode and copying the .uf2 works but I haven't been 
able to get the 3 pin SWD interface with a Raspberry Pi 5 working. Not 
insurmountable but the documentation isn't great. Getting to the BOOTSLE 
mode requires holding down a button while unplugging/plugging the microUSB 
which is cumbersome. It's even more complicated for a generic computer 
without the Pi's GPIO pins.

Loading MicroPython the first time is similar but then the device comes up 
on /dev/ttyACM0 and is faster to develop since it doesn't require 
recompiling every time. 

I've got another Pico W that I may try with one of the Forth variants. 

Working with C++ and the Arduino Nano 33 BLE Sense was much easier but it 
has the mbed RTOS as a loader. Unfortunately mbed is going away. 

Digging into the Forth internals is instructive. When compared to CPython 
it is either elegant or a kludgy mess depending on how much you hate 
Forth.