The showcase
Mid-size programs that each stress a different part of Raku++ — together they answer "what can it actually build?"
Every one of them runs under the interpreter and compiles to a standalone native binary. Five are interpreters for other languages, and run in your browser — the playground has them as examples. For single-file programs rather than projects, see the examples.
Language power
lisp runs in the browser
A grammar + a tree-walking evaluator. Interpreter that runs Scheme files or a REPL.
js runs in the browser
A full precedence ladder, closures, classes. Interpreter that runs JavaScript/TypeScript files or a REPL.
forth runs in the browser
A stack machine + word dictionary. Interpreter that runs Forth files or a REPL.
perl runs in the browser
Sigil variables, context, regex. Interpreter that runs Perl 5 files or a REPL.
python runs in the browser
The off-side rule, via an INDENT/DEDENT tokenizer. Interpreter that runs Python 3 files or a REPL.
Parsing
markdown
A grammar that emits HTML. Converter: Markdown in, a styled page out.
json
A grammar that round-trips data. Parse, pretty-print / minify, and query JSON.
Deployable
pastebin
A hand-written HTTP server on raw sockets. Native binary you point a browser at.
rakus
A general static HTTP file server. Point it at a folder, open it in a browser.
Concurrency
chat
Many clients, one thread each. TCP chat server you connect to with nc.
Protocols
kvstore
A key-value store with its own text protocol. Redis-style TCP server you drive with nc.
Ecosystem
modinfo
17 zef distributions doing the work. Inspects Raku distributions: graph, validation, reports.
jsonreq
Our own modules composing. Curl+jq for JSON APIs: request, query, pretty-print.
C libraries
sqlite
NativeCall and a raw-mode terminal. Database client: query, browse, dump; the real libsqlite3 does the work.
In the browser
web
The pure showcases running client-side on the WebAssembly build. Three little apps — a live Markdown editor, a JSON beautifier, a regex tester.
Software that already existed
The showcases were written here, for Raku++. live is the opposite discipline: whole tools from the Raku ecosystem — other people's work — installed the way any user installs them and run unmodified, their output checked against Rakudo's. How that works, and what it has found →