Chuck Moore, the creator of Forth, has spent decades trying to make computers do more with less. His colorForth site is a surviving notebook from that obsession: a programming environment where color replaces much of the punctuation and syntax that other languages keep adding.
Visit Chuck Moore’s colorForth site
The basic idea is stranger than ordinary syntax highlighting. In colorForth, the colors are part of the language. Red introduces a new definition, green marks compiled words, yellow marks words to execute immediately, and other colors carry other functions. The source is not ordinary text with decorative coloring painted over it afterward. The color participates in how the code is interpreted.
A Programming Environment That Barely Exists
Moore’s colorForth pages describe a system that could run under Windows or boot without a conventional operating system. The core was measured in kilobytes rather than megabytes, and the keyboard layout used a compact 27-key arrangement based on Dvorak.
The source representation was equally unusual. Words were stored in a pre-parsed compressed form with bits reserved for their color and function. Programs were organized into small blocks rather than ordinary text files. The whole thing reflects Moore’s long-running argument that software becomes more understandable when unnecessary layers are removed rather than hidden behind still more layers.
That makes colorForth interesting even if you never intend to use it. It is an unusually complete example of a programmer questioning assumptions that most software simply inherited.
Then He Used It to Design Chips
The site also preserves material about OKAD, Moore’s VLSI design tools. He describes a remarkably small colorForth codebase capable of laying out and simulating integrated circuits and generating manufacturing data. The surrounding pages lead into his work on highly parallel processors built from many tiny Forth-oriented cores.
There is also historical material reaching much farther back, including Moore’s early book Programming a Problem-Oriented Language. That turns the site into more than a download page for one eccentric language. It connects several decades of the same design philosophy: small programs, direct control and aggressive skepticism toward complexity for complexity’s sake.
Modern software development rarely rewards that kind of stubborn minimalism. That is precisely why the surviving pages are useful. They document what happens when someone keeps asking how much of the conventional computer stack is actually necessary.