Under the Hood
For everyone who wants the details: how Kiste works — and where the language stands.
How Kiste works
Kiste has three ways to run your program — from an instant start while learning to a fast, standalone file.
kiste run Runs your program instantly, with no build step — ideal for learning and experimenting. It supports the entire language.
kiste run --vm First translates the program into compact instructions and runs those — noticeably faster than running directly, when you want more speed without building a file yet.
kiste build Turns your code into a real, standalone program file (an .exe on Windows) that runs without Kiste. The fastest path — built programs are many times faster than running directly.
To build, Kiste uses the proven LLVM toolchain — the same foundation that big languages like Rust or Swift build on. The result is a standalone file with no further dependencies: build it once, hand it to anyone, and it runs.
Kiste manages memory for you automatically — there’s nothing to free by hand. In graphical programs the cleanup runs in small steps so the picture doesn’t stutter.
Kiste runs on Windows and Linux; a macOS version is planned.
Where Kiste stands
Kiste combines the easy on-ramp of a language like Python with the strength of compiled languages. Built as a native file, Kiste holds its own against established languages — in the test below it lands behind the low-level languages C and Rust and ahead of every other language measured (including LuaJIT, C#, JavaScript and Python). This isn’t meant to put anything down (the others are great languages too) — it just helps you place where Kiste stands.
Measured, not claimed
The same small program — computing the 35th Fibonacci number recursively — across several languages and Kiste modes, measured on an ordinary Windows PC:
| Language / mode | Time for fib(35) |
|---|---|
| C (gcc -O2) | 0.015 s |
| Rust 1.95 | 0.023 s |
| Kiste — built natively | 0.036 s |
| LuaJIT 2.1 | 0.063 s |
| C# (.NET 10) | 0.066 s |
| JavaScript (Node.js 24) | 0.088 s |
| Lua 5.4 | 0.36 s |
| Python (CPython 3.14) | 0.82 s |
| Kiste — bytecode VM | 7.2 s |
| Kiste — tree-walker (direct) | 19.2 s |
A single, compute-heavy microbenchmark — not a general ranking; the numbers shift with the program, the machine and the language version (for the fastest entries, program startup time counts too). What matters is the order of magnitude: built as a native file, Kiste lands behind the low-level languages C and Rust — and ahead of LuaJIT, C#, JavaScript and Python; a strong result for such a young language. The tree-walker is deliberately built for an instant start with no build step, not for speed — ideal while learning.
Like Go, Kiste produces standalone files that run without a separate runtime. Unlike Rust, though, simplicity comes first by design — automatic memory management instead of manual control, German keywords, clear error messages.
Kiste is a young language built by a single developer — no corporation behind it. The focus is deliberately on making programming accessible, not on owning every conceivable feature.