Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.forth > #135489

Only Forth For Livecheck, No C

From Terry Porter <techman001@eternal-september.org>
Newsgroups comp.lang.forth
Subject Only Forth For Livecheck, No C
Date 2026-08-30 03:09 +0000
Organization A noiseless patient Spider
Message-ID <11706u3$3obgi$1@dont-email.me> (permalink)

Show all headers | View raw


Why does a tool that checks your code against a real microcontroller as
you type — over a debug wire, live, in the editor — only work with
Forth, and not C? This episode answers that question, and the answer is
not what you'd expect. It's not a language snobbery. It's physics.

The story begins in 1984, with a technician programming a bottle-filling
machine in raw machine code — hexadecimal digits typed by hand on an
Intel 8085 with a hex keypad. Painful. Then an assembler for the 6800,
and life became smooth as silk. Then PIC microcontrollers and a simple
C-like language that sold some simple products. Then the project that
broke him: an automatic truck lubrication system, very profitable if it
worked — and it didn't. The hardware was sound; the software let him
down. If he'd had Forth, which he hadn't discovered yet, it would have
been a different story.

That story is the key to everything. Forth runs on the chip as a
resident interpreter — you type a line, the silicon answers in
milliseconds. C is cross-compiled and flashed — the feedback loop is
tens of seconds. And that difference is the whole ballgame, because of
*context*.

A slow feedback loop kills context. It kills the human developer's train
of thought, and it kills an AI's context window the same way — make a
change, flash, wait thirty seconds, and the AI has forgotten what it was
doing. It's like driving a Mars rover from Earth: you see the crater on
the video feed, you send "stop," but by the time the signal crosses the
distance and the video comes back, the rover is already in bits at the
bottom of the crater. The command isn't wrong — it's late. AI works fine
with regular C on a desktop, where the loop is fast. But embedded C's
compile-flash-reset cycle is the context killer — for the human and the
AI alike, driving every rover from Earth, and the craters keep winning.

That's why LiveCheck only exists for Forth. It's designed to work with
AI, and AI needs a fast feedback loop to hold a thread of thought about
the silicon. Only an interactive on-chip language can give it one. This
episode explains exactly why you'll never see a LiveCheck for C — and
why that's not a limitation, but the point.

Produced with the help of AI without which this video would not have
been possible

(Context: I'm Terry, a 72-year-old electronics technician — fifty years
of soldering, circuits and oscilloscopes, Forth since the 90s. I dictate
my notes and an AI helps me write them up clearly, but the actual bench
work — the registers, the LEDs, the clocks, the measurements — is mine,
done live.)

Back to comp.lang.forth | Previous | Next — Next in thread | Find similar | Unroll thread


Thread

Only Forth For Livecheck, No C Terry Porter <techman001@eternal-september.org> - 2026-08-30 03:09 +0000
  writing style with AI (was Re: Only Forth For Livecheck, No C) Kragen Javier Sitaker <kragen@canonical.org> - 2026-08-31 09:17 -0400
    Re: writing style with AI (was Re: Only Forth For Livecheck, No C) Terry Porter <techman001@eternal-september.org> - 2026-08-31 21:39 +0000
      Re: writing style with AI (was Re: Only Forth For Livecheck, No C) Kragen Javier Sitaker <kragen@canonical.org> - 2026-09-11 14:30 -0300
        Re: writing style with AI (was Re: Only Forth For Livecheck, No C) Terry Porter <techman001@eternal-september.org> - 2026-09-12 09:36 +0000
    Re: writing style with AI (was Re: Only Forth For Livecheck, No C) dxf <dxforth@gmail.com> - 2026-09-01 07:59 -0400
      Re: writing style with AI (was Re: Only Forth For Livecheck, No C) marcel hendrix <mhx@iae.nl> - 2026-09-01 13:34 -0400
        Re: writing style with AI (was Re: Only Forth For Livecheck, No C) dxf <dxforth@gmail.com> - 2026-09-02 17:08 +1000
        Re: writing style with AI (was Re: Only Forth For Livecheck, No C) antispam@fricas.org (Waldek Hebisch) - 2026-09-02 11:52 -0400
          Re: writing style with AI (was Re: Only Forth For Livecheck, No C) albert@spenarnc.xs4all.nl - 2026-09-02 20:09 +0200
      Re: writing style with AI (was Re: Only Forth For Livecheck, No C) Kragen Javier Sitaker <kragen@canonical.org> - 2026-09-01 13:34 -0400
    Re: writing style with AI (was Re: Only Forth For Livecheck, No C) Hans Bezemer <the.beez.speaks@gmail.com> - 2026-09-07 12:43 +0200
      Re: writing style with AI (was Re: Only Forth For Livecheck, No C) Kragen Javier Sitaker <kragen@canonical.org> - 2026-09-11 15:31 -0300
        Re: writing style with AI (was Re: Only Forth For Livecheck, No C) Hans Bezemer <the.beez.speaks@gmail.com> - 2026-09-15 19:58 +0200

csiph-web