← the front page · Raku++ in use
The Raku language, in use
Two kinds of evidence, and neither of them is slides. Code running under the engine here — complete programs with live editors, mid-size projects, and whole tools from the ecosystem driven unmodified — and, elsewhere, software other people built that reached for the engine on its own. Every output on these pages was printed by the program beside it, captured from the interpreter itself.
Try it yourself
Code to read and run #
Not snippets: working code, on three shelves — and only the first two were written here. Complete programs you can edit and re-run on their own page; mid-size projects that answer "what can it actually build?"; and then other people's software again, whole tools installed from the ecosystem the way any user installs them and run unmodified. Nothing on that third shelf is in this repository either: what is kept there is the harness that drives it.
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
Sixteen 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.
Elsewhere
Adoptions #
Nobody here wrote these, and nobody here was asked: a paclet in Wolfram's own repository, a browser playground that offers Raku++ as one runtime among four, a Guix channel, a port of the release matrix to somebody else's CI. Each link goes to whoever built it.
Raku Playground ↗
Offers rakupp as one of four runtimes, in the browser.
Fernando Correa de Oliveira