Deutsch   English   Français   Italiano  
<lno9vqF368kU2@mid.individual.net>

View for Bookmarking (what is this?)
Look up another Usenet article

Path: ...!news.mixmin.net!weretis.net!feeder8.news.weretis.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: rbowman <bowman@montana.com>
Newsgroups: comp.os.linux.misc,alt.folklore.computers
Subject: Re: The joy of FORTH (not)
Date: 22 Oct 2024 00:29:46 GMT
Lines: 23
Message-ID: <lno9vqF368kU2@mid.individual.net>
References: <pan$96411$d204da43$cc34bb91$1fe98651@linux.rocks>
	<vdnvk0$49ai$2@dont-email.me>
	<o8icnRRnt4ChGGL7nZ2dnZfqn_idnZ2d@earthlink.com>
	<vdo3j6$4q92$1@dont-email.me> <lm9kg6Ft2vgU2@mid.individual.net>
	<vdpi96$bgk6$7@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>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Trace: individual.net ryHvc90wyuhHvxGhEIi9LQwOo3HEm/wy5UkF9DDBHSv6rJ6oLp
Cancel-Lock: sha1:EmT0aYmh5Rogu2X89XtErqMPo7w= sha256:Uxc0r7QSAi7NuBiM0cpE9t3rpPTiVgwNzb8Vbz/ogv8=
User-Agent: Pan/0.149 (Bellevue; 4c157ba)
Bytes: 2584

On Mon, 21 Oct 2024 23:12:08 -0000 (UTC), Lawrence D'Oliveiro wrote:

> On Mon, 21 Oct 2024 15:16:52 -0700, John Ames wrote:
> 
>> ... "cross-compile on a separate machine" as a development process adds
>> steps that aren't necessary in an interactive, self-hosting
>> environment,
>> where you can debug, tweak, and re-test right in place.
> 
> Which you can anyway, with any decent build setup. Just press one key in
> your editor to save, build, reload and run.

At least with the Pico the reload part means you need to use the debugging 
interface or unplug/plug the USB cable while holding the BOOTSEL button. 
The Pi exposes the GPIO pins for the debuger but a generic Linux box needs 
another piece.  Compiling the traditional blink programs isn't 
instantaneous either.

One of the advantages of MicroPython for development is the firmware 
allows the Pico to come up as /dev/ttyACMxxx so you can simply write 
the .py file to the device.

Just because you have no use for Forth don't write it off.