Wolang is open source
Wolang, the statically typed, compiled language we have been building for MowoEngine, is now open source under Apache-2.0. It has effects in its signatures, units in its types, components and systems the compiler schedules, three execution tiers that must agree, and a C API for embedding. Here is what it is, what works today, and how to help.

Wolang is the programming language we have been building alongside MowoEngine, and as of today its compiler, runtime, standard library and tools are open source under the Apache-2.0 licence.
Repository: github.com/MowoGames/Wolang Documentation: mowoengine.com/docs/wolang
What Wolang is
A statically typed, compiled, general-purpose language with gamedev-grade ergonomics. It is its own project: the compiler and libraries do not depend on any engine, and MowoEngine is one of the hosts it can be embedded into.
need std.io.{Print}
fun main() uses io {
const name = "world"
Print("hello, {name}")
}Three things are visible already. need imports names one module at a time. uses io is the function stating what it may do: printing is an effect, and the compiler checks effects through the whole call graph. And {name} is string interpolation.
What makes it different
Wolang takes abilities, exhaustive match, Result-style errors, comptime and optionals from the usual places. These five are what it is built around:
| Effects and capabilities | A signature states what a function may do: uses io, alloc, rand. One mechanism covers determinism, allocation-free hot paths, sandboxed mods and compile-time evaluation. |
| Units in the type system | 10m / 2s is a velocity. Adding a length to a time does not compile, and none of it costs anything at run time. |
| Layout polymorphism | soa []Particle stores one array per field, aos []Particle stores records. The layout belongs to the storage, not the type. |
| State machines | machine, state and on Interact after 3s -> Closing are language constructs, and unreachable states are a compile error. |
| Reactive values | derived fields recompute when their inputs change. |
We will go through each of these in a follow-up post.
What works today
This is not a design document. The language runs, and it is tested hard:
- Three tiers that must agree. An interpreter is the reference, a just-in-time tier serves
wolang run, and an ahead-of-time tier through LLVM serveswolang build. A differential fuzzer generates programs and compares all three. - Five platforms: macOS (arm64, x86-64), Linux (x86-64, arm64) and Windows x86-64, with cross-compilation to Windows, Linux, WebAssembly and RISC-V.
- A standard library of 34 modules, written in Wolang: JSON, TOML, YAML, INI and CSV, regular expressions, SHA-2 and HMAC, deflate and gzip, time zones, processes and threads.
- Packages beyond
std: an HTTP server and client (about 54,000 requests a second on one thread), TLS, a crash-safe key-value store, and a window, GPU and audio layer. - Tooling: a formatter, a language server with support for VS Code, Zed, Neovim, Sublime Text, Emacs, Helix and JetBrains IDEs, a REPL, a Debug Adapter Protocol debugger, a profiler, record and replay, and a C header binder.
- Tests: 692 compiler unit tests and 184 library tests run on every tier, and every code sample in the documentation is compiled by CI.
Try it
curl -fsSL https://raw.githubusercontent.com/MowoGames/Wolang/alpha/install.sh | sh
wolang new hello && cd hello && wolang run .On Windows:
irm https://raw.githubusercontent.com/MowoGames/Wolang/alpha/install.ps1 | iexThen read the tour, which shows the whole language in about half an hour.
What it does not have yet
We would rather you hear this from us. There are no GPU kernels yet, no HTTP/2, no vectorisation or alias analysis, and reference cycles between classes leak unless you break them with weak. Dependencies are pinned to exact revisions with no version ranges. STATUS.md is the honest, current list.
Why open source, and why now
A language lives or dies by the people who write programs in it, and a compiler gets better fastest when many people hand it programs its authors never thought of. Wolang has reached the point where the core design is settled, there are more than two hundred numbered decisions recorded with their reasons, and the next work is breadth: libraries, platforms, editors, optimisation and documentation. That is work a community does better than a single team.
How to help
- Use it and report what breaks. The most valuable bug report is a program where
wolang runandwolang run --interpretdisagree. - Pick up a starter task. CONTRIBUTING.md has a list sorted by size, from date formatting in
stdto alias analysis in the IR. - Ask and discuss. Questions and language ideas go to GitHub Discussions.
- Star the repository if you want to follow along.
Next in this series: the five ideas Wolang is built around, how three tiers keep the compiler honest, and the road to Wolang 1.0 inside MowoEngine.