← the front page · Raku++ in use
The language, in use
Not slides and not snippets: working code, on three shelves. Complete programs you can edit and re-run on their own page; mid-size projects that answer "what can it actually build?"; and software other people wrote, installed from the ecosystem and run unmodified. Everything here is real — every output was printed by the program beside it, captured from the interpreter itself.
Raku by example
Twenty-four self-contained programs, one page each: the README's story, the full source in a live editor, and what it prints. Twenty-one run right on the page, in your browser; the three that need real threads or sockets say so and show their native output.
The showcase
Fifteen mid-size projects, each stressing a different part of the language: interpreters for five other languages, servers on raw sockets, a SQLite client over NativeCall, seventeen ecosystem distributions composing. Each page is the project's own README; each project compiles to a standalone binary.
A Scheme interpreter · the SQLite client · a pastebin server
Software that already existed
The opposite discipline: whole tools from the Raku ecosystem — other people's work — installed the way any user installs them, run unmodified, and diffed against Rakudo's output. Code nobody wrote for this implementation reaches for corners nobody here would have thought to test.
The example outputs are captured from the native interpreter and committed — a page cannot show output its program did not produce — and every deterministic capture is verified byte-identical under Rakudo. The five showcase interpreters are also loaded in the playground, program in the input box, ready to run.