Published on 2026-02-09 written by pepe and corrected by lluma

Why Janet in the Thickets

Thicket Web Mind emanated from Janet.

Not because Janet has the right features, but because it does not fight the shape of the system. The methodology emerged naturally while working with the language, not as a goal imposed on it.

Janet produces single, self-contained executables, which fits the idea of compile-time configured Symbionts. Its small runtime and fast startup make it practical to run many small machines instead of a few heavy ones.

Fibers support long-running, cooperative behavior without imposing complex concurrency models. State is explicit, mutation is visible, and ownership is clear — which makes local reasoning inside a Thicket possible.

Janet’s C-level performance comes without runtime sprawl. Its embeddability allows creation to live inside the system itself. The language stays a tool, not a framework gravity well.

Its Lisp nature makes language part of design, not just implementation. Naming, structure, and behavior remain close. The REPL encourages exploration without lock-in, and the core remains small enough to stay readable.

Janet does not demand architecture.

It allows one.