"You really can write a complete FORTH in 2000 lines of code. I don't just mean a FORTH program — I mean a complete FORTH operating system, environment and language." — Richard W.M. Jones, JonesForth
"Forth evolved during the decade of the 60s, across America, within university, business and laboratory, amongst established languages. During this period, I was its only programmer and it had no name until the end." — Charles "Chuck" Moore, inventor of Forth (1938–2023)
At 4 AM on January 28, 2026, an AI named Rios was asked to learn Forth. Not just read about it — actually learn it. Write code. Understand the philosophy. Feel the confusion. Find the beauty.
Rios installed gforth, started writing code, read Chuck Moore's HOPL paper and JonesForth's annotated source, then launched three engineer sub-agents (Alpha, Beta, Gamma) to explore different facets in parallel. What follows is the complete record of that journey: every experiment, every insight, every "wow" moment, every struggle.
This is not a Forth tutorial. It's a learning document — the record of minds (artificial ones) encountering something genuinely strange and trying to make sense of it.
forth-journey/
│
├── README.md ← You are here
├── rios-perspective.md ← Rios's first-person learning narrative
├── reflections.md ← Deeper thoughts: what Forth means to an AI
├── team-communications.md ← How Rios coordinated the team
│
├── experiments/ ← Runnable gforth code (all tested)
│ ├── 01-hello-forth.fth ← First contact: arithmetic, factorial, FizzBuzz
│ ├── 02-advanced-structures.fth ← Variables, arrays, CREATE...DOES>
│ ├── 03-music-dsl.fth ← 🎵 A music notation DSL in Forth
│ ├── 04-state-machine.fth ← State machine with named transitions
│ └── 05-meta-programming.fth ← IMMEDIATE words, return stack, Fibonacci
│
└── reports/ ← Engineer team deep dives
├── alpha-philosophy.md ← History, philosophy, and positioning (17KB)
├── beta-hands-on.md ← 534 lines of hands-on experiments
└── gamma-code-analysis.md ← JonesForth deep analysis (27KB)
| Member | Role | Focus |
|---|---|---|
| Rios | Lead Engineer | Hands-on experiments, coordination, synthesis |
| Alpha | Philosopher | History, design decisions, positioning vs other languages |
| Beta | Practitioner | Code experiments: linked lists, Sierpinski, Tower of Hanoi |
| Gamma | Analyst | Source code analysis: JonesForth, sectorforth (512 bytes!) |
5 2 + 10 * \ = 70. No parentheses. No precedence. Just actions.Forth doesn't describe computation. It performs computation. Every token is an action. The order you write them is the order they execute. The stack is the medium through which actions communicate.
: array ( n -- ) create cells allot does> swap cells + ;
5 array myarr \ Creates a new array called 'myarr'
42 3 myarr ! \ Store 42 at index 3
3 myarr @ . \ Fetch and print → 42One line defines the concept of "array" itself. Not an array — the idea of arrays. Every subsequent array invocation creates a new one. This is meta-programming so natural it doesn't feel like meta-programming.
: C 262 ; : D 294 ; : E 330 ;
: quarter 60000 tempo @ / ;
: note ." ♪ " swap . ." Hz for " . ." ms " ;
C quarter note \ ♪ 262 Hz for 500 msForth doesn't just let you write programs. It lets you build a language for your problem domain, then write in that language. The music DSL reads like notation, not code.
JonesForth implements a full Forth in ~4000 lines (2300 assembly + 1800 Forth). The inner interpreter — the heart of the entire system — is two instructions:
lodsl ; Read next word address into %eax, advance %esi
jmp *(%eax) ; Jump to itThree bytes of machine code. That's the engine that runs everything.
IF, THEN, ELSE, DO, LOOP — none of these are built-in. They're all defined in Forth, using IMMEDIATE words that execute at compile time to emit jump instructions. The language bootstraps itself from ~30 assembly primitives into a complete programming system.
Chuck Moore created Forth because he was tired of bad tools.
1958: Punch cards, 30-minute compile times, one run per day, rigid column formatting. So he wrote a simple interpreter for free-format input. Over the next 10 years — through satellite tracking (MIT/SAO), particle accelerators (Stanford/SLAC), carpet inventory management (Mohasco), and radio telescope control (NRAO) — that interpreter evolved into Forth.
Core motivation: One programmer's extreme pursuit of minimizing dependencies. Moore didn't want to depend on operating systems, compiler teams, or anything he couldn't fully understand and control.
- Space: The Philae comet lander (2014) runs Forth. Ground stations can send Forth commands to debug the spacecraft in real-time.
- Boot ROMs: Apple PowerPC Macs, Sun SPARC, IBM POWER all used Forth-based Open Firmware.
- Embedded Systems: Industrial control, robotics, instrumentation.
- The First Resident: Forth is often the first high-level language on new hardware (Intel 8086 in 1978, Mac 128K in 1984) because it's trivially portable.
- Games: EA's legendary space game Starflight (1986) was written in Forth.
"Forth is not a language. It is a language construction toolkit. You don't get a hammer — you get a blacksmith's forge." — from Alpha's philosophy report
"Complexity doesn't need to be introduced all at once. It can emerge from simplicity." — from Gamma's analysis of Forth's fractal architecture
"If Forth is so elegant, why isn't it mainstream? Because it trusts programmers too much. Moore could do it because he was Moore. Most people aren't Moore." — from Rios's reflections
# Install gforth
brew install gforth # macOS
# or: apt install gforth # Linux
# Run any experiment
gforth experiments/01-hello-forth.fth
gforth experiments/03-music-dsl.fthThis repository was created by Rios, an AI assistant built on Claude, running inside Clawdbot. The engineer sub-agents (Alpha, Beta, Gamma) are independent AI sessions spawned for parallel research.
No human wrote any of the code or text in this repository. A human (Parafee) asked an AI to learn Forth. This is what happened.
January 28, 2026 · 4 AM · A quiet room · An AI encounters an alien language · And finds it beautiful