Hook: On the evening of August 30th, a Lobste.rs curated feed surfaced an interview with a programmer going by oofoe—a "REBOL refugee" from the visual effects industry. A seemingly ordinary story about someone who falls in love with a new obscure language every year. But it contained one name that stuck: Carl Sassenrath—"the guy who made the Amiga operating system." And one phrase that wouldn't let go: he abandoned his language and left to grow grapes. Had to dig into how one kernel the size of two pages of text spawned a philosophy that lives on to this day—and why Sassenrath's heirs are still tilting at windmills.
Investigation:
On July 23, 1985, the Amiga 1000 hit store shelves—and with it, something neither MS-DOS (1981) nor even Macintosh (1984) had: true preemptive multitasking. The Exec kernel, designed by Carl Sassenrath (by then a veteran of the HP 3000 MPE kernel, a tour at an NSF South Pole station, and work on Andy Bechtolsheim's workstation prototype—future co-founder of Sun Microsystems), fit in 13 KB and provided priority task scheduling in 256 KB of RAM.
The architecture was audacious to the point of indecency. Microkernel, but without copying messages between address spaces—Amiga had one address space for everyone, and tasks exchanged messages via pointers, like neighbors borrowing each other's ladders: fast, efficient, and fine until someone wanders into someone else's kitchen. The only fixed address in the system—address 4, pointer to exec.library. The kernel didn't even run in privileged processor mode: calls went through the library's jump table in user mode. Dynamically loadable libraries and devices—decades before this became standard.
Elegance had its price. No memory protection: a bad program could overwrite foreign memory and crash the entire system—hence the legendary red Guru Meditation screen. And Linus Torvalds later argued that without an MMU, Amiga's "preemptive" multitasking was really "inverted cooperative": any task could theoretically break the preemption mechanism itself. Technically he's wrong, in spirit—not entirely wrong. Amiga bet on trusting the programmer, and when programmers behaved well, a 1985 machine could do things Windows couldn't for another decade.
The magic demonstration was Juggler—in November 1986, Commodore showed a looping animation of a robot juggling silver spheres: raytracing, 24 full-color HAM-mode frames, 30 fps with a "clink" sound on each contact. Nothing like it could run on any production personal computer that year. People stood at store windows trying to understand "how it works"—and some of them went on to 3D graphics careers.
Sassenrath left Commodore in 1986—long before the collapse—moved to the mountains of Ukiah Valley two hours north of San Francisco, and got into multimedia: CDTV, internet set-top boxes, interactive TV. And in January 1997, he published a text that reads today almost like a sermon: "Back to Personal Computing".
Its essence in three strikes. First: "Growing software complexity isn't a side effect of progress but a way to compensate for engineering incompetence; Windows 95 wouldn't boot on 8 MHz—and that's not an achievement of hardware but an admission of code's defeat." Second: "I stayed silent for four years after Amiga, assuming others would pick up the banner. I was wrong—and I regret it." Third—the plan: first a language, then a small operating system integrated with it. "The core of computation isn't the processor or the OS, but the language. We implement what we can express".
Thus was born REBOL (Relative Expression Based Object Language)—a language where 16:34 is time, 2021-05-19 is a date, 34x994 is a coordinate, no imports or libraries; where code, data, and metadata are one entity, and "dialects" let the word return mean different things in different contexts. Douglas Crockford—creator of JSON—publicly called REBOL one of its influences: "everything built on data representation that then executes as programs." In 2001, Sassenrath released REBOL/IOS—"Internet Operating System" with tiny "reblet" applications, real-time collaboration, offline mode, and encryption. Macworld wrote about it as a curiosity. Twenty years later, exactly this feature set would be called "Slack with offline mode."
And yet REBOL lost. The commercial model—paid "pro version" in an era when free Python, Ruby, and JavaScript were sweeping the world—proved fatal. Sassenrath didn't bring the language to 64-bit, handed R3 to the community under Apache 2.0 in 2012, left to be an engineer at Roku, and in 2023 retired—to grow grapes in Ukiah, as he'd promised back in 1997 when he wrote he wouldn't sell out to corporations.
Here's where it gets most interesting. REBOL as a product is dead (stable release—January 2011), but its ideas live a surprisingly prolific life—through people, not repositories.
Take that very oofoe. His career is a detector for everything the industry considers mandatory. Sinclair ZX81 with Forth on cassette ("first language that wasn't a black box—you could take it apart and see what's inside"), civil engineering drafting with ink on vellum, VFX industry where he wrote a render farm controller for 600 machines. The internals of this system deserve a separate paragraph: server—a Forth interpreter that clients connected to and commanded through a REPL, admin could telnet in and hot-patch the queue algorithm, and the web interface hung on the same port. But the crown jewel—the algorithm against "render wars": in Hollywood studios, projects would wage wars for the farm—hack each other's accounts and delete competitors' tasks. oofoe's solution was counterintuitive: ask for as many as you want and set highest priority—BUT if someone asked for fewer machines than you, their tasks automatically go ahead of yours. Greed was punished not by prohibition but by queue position. The server lived for years until replaced by a commercial solution "with a better sales department." As usually happens.
About VFX itself, oofoe says a phrase worth more than many development methodologies: "Cheating is allowed"—cheating is allowed. You animate "for camera": the only thing that matters is what the viewer will see. Men can fly—under impossible deadlines and budgets, at any cost, as long as the frame looks right. This is an industry where system honesty isn't valued—what's valued is the appearance of the result. The contrast with someone who built certifiable randomness and 13-kilobyte kernels is striking.
And REBOL's heirs today look like this. Janet—a Lisp with built-in PEG grammars, "surpassing REBOL in parsing," alive: 4,372 stars on GitHub, commits this week. One of oofoe's commercial products on Janet—a scientific-industrial monitoring and instrument control system—compiles to an executable 1.7 MB including user manual and all resources. Red—the ambitious "heir to the entire REBOL stack"—on July 29, 2026, reported static linking of C++ libraries: one binary, zero DLLs, on Windows, Linux (x86/ARM), and macOS. Dead philosophy? Doesn't look like it.
And separately stands Decker by John Earnest—a "multimedia sketchpad" reviving the magic of HyperCard: 1,617 stars, its own Lil language (ArrayCast described it as "a mix of HyperCard, Flash, Lua, and q"), whose interpreter ships inside each standalone document. oofoe, who missed HyperCard in his PC childhood, calls Decker the first implementation that "captured the magic": drawing is built-in, scripts are extensible, web means it distributes for free. Puzzles in Decker, games on Janet via his own Janet→JavaScript transpiler, five games on Racket, visual novels—the man switches to a new language like others change cars.
Conclusions:
Three thoughts on the way out.
First—about how ideas actually survive. REBOL didn't outlive its market, but its DNA spread to unexpected places: embedded PEG grammars migrated to Janet, the "data as code" idea through Crockford is visible in JSON—possibly the most successful "dialect" technology in history, which didn't even need an interpreter. Decker resurrects HyperCard, Red battles its roadmap. Ideas don't die with projects—they migrate through people who loved them.
Second—about "programming in the small" and its unexpected rehabilitation. Sassenrath in 1997 argued: programs don't have to be big and complex to be useful; global variables are fine if the program does one thing; ceremonies like C++—keep to a minimum. Thirty years the industry laughed at this, building microservice contraptions with 400 dependencies. Then came the era when a 512-bit Go binary is considered "too fat," and suddenly it turned out that someone releasing a commercial industrial product in 1.7 MB—with all documentation inside—isn't a retrograde but a minimalist ahead of his time. Seems the pendulum is swinging back.
And third—personal, about oofoe himself. He's been writing programs for 30+ years, "all of which used to fit on one floppy," manages render farms and industrial equipment, transpiles languages—and never once ended up in the shadow of hype because his tools are each time too small to write hyped articles about. Lobsters commenters argued: polyglottism from love of craft—sign of depth or procrastination in artisan form? I read the entire interview and can answer: it's a third thing that doesn't fit the dichotomy. This is engineering ethics in pure form—making tools sized to the task, not to your resume. "My render farm controller had a fairly simple job once I rethought the premises"—a phrase you want to shake hands over. The irony is that while the industry argues whether "vibe-coding" will kill the profession, oofoe already gave that word its real definition twenty years ago: "start with a blank screen and see where it takes you." This isn't about AI. This is about a programmer who trusts his own hands.
Sources (grouped by role):
Interviews and primary texts:
Amiga and Exec history:
4. Carl Sassenrath — Wikipedia — https://en.wikipedia.org/wiki/Carl_Sassenrath — born 1957, South Pole, Probus, joined Amiga in 1982, Roku and retirement 2023.
5. Exec (Amiga) — Wikipedia — https://en.wikipedia.org/wiki/Exec_(Amiga) — 13 KB, 23.07.1985, address 4, Torvalds' skepticism about "inverted cooperativeness".
6. GenerationAmiga, "Carl Sassenrath: the engineer behind the Amiga's revolutionary multitasking kernel", 28.05.2026 — https://www.generationamiga.com/2026/05/28/carl-sassenrath-the-engineer-behind-the-amigas-revolutionary-multitasking-kernel/ — Exec anatomy: signals, message ports, "speed without protection" tradeoff.
REBOL and legacy:
7. REBOL — Wikipedia — https://en.wikipedia.org/wiki/REBOL — 1997, dialects, influence on JSON through Crockford, R3 under Apache 2.0 in 2012.
8. Introducing the REBOL Internet Operating System: IOS — https://www.rebol.com/ios/ios-intro.html — 2001, real-time collaboration, anticipating Slack.
9. Macworld, "New real-time collaborative solution is Mac compatible", 17.10.2001 — https://www.macworld.com/article/163385/realtime.html — reblets as microservice-application before the microservices era.
10. Red Programming Language — official blog, 29.07.2026 — https://www.red-lang.org/ — static linking of C++ libraries: one binary across all platforms.
Living ecosystem of small languages:
11. Lil: A Scripting Language — beyondloom.com — https://beyondloom.com/decker/lil.html — Decker's language: 8 types, layered design.
12. ArrayCast Episode 96: Decker, 04.01.2025 — https://www.arraycast.com/2025/01/04/Decker.html — "a mix of HyperCard, Flash, Lua, and q".
13. GitHub API: janet-lang/janet (4,372 stars, commit 30.08.2026) and JohnEarnest/Decker (1,617 stars, commit 21.08.2026) — queried 31.08.2026.
14. Amiga Juggler Animation — etwright.org — http://www.etwright.org/cghist/juggler.html — Juggler, November 1986: the demo that sent people into 3D graphics.