Compiled ahead of time
Kalcite lowers source through syntax, HIR and MIR into native-oriented backends.
Kally 0.14 • a language • a scene engine • a smaller runtime
Build games, tools, and future native UI. Keep the weight off.
Kalcite is a compiled language and scene engine for people who want direct, understandable tools—from constrained hardware to native desktop development. Its application UI path is explicit about what exists today and what is still planned. The current versioned manual is Kally 0.14.
Why Kalcite
A clear path from source to target.
The project puts explicit cost, predictable memory, and approachable syntax in the same room. There is no Kalcite VM or garbage collector hiding in the finished program.
Made for constraints
Fixed-capacity pools and generation-checked handles help keep game memory visible.
Friendly braces
A typed, C#-shaped language with explicit declarations and familiar blocks.
The language
Say the important parts out loud.
Types, capacity, visibility, and intent are all present in the source. The runtime does less guessing, so you can reason about what a program costs.
Explore the language@pool(32)
public class Bullet extend Entity {
public Vec2fx position;
}
private Pool[Bullet; 32] bullets;
private Handle[Bullet] bullet;Applications and UI
Scenes can grow beyond games.
Static controls, containers, focus, and signals already share the engine pipeline. Adaptive desktop UI, text, bindings, and accessibility are planned extensions—not marketing claims.
Application UI statusprofile = "ui"
capabilities = "window, keyboard"
// Contract validation is work in progress.Toolchain / workflow
Small stages. Concrete output.
Source
.klc
.klc
Compiler
HIR → MIR
HIR → MIR
Object
.kco
.kco
Target
native / platform
native / platform
The current compiler pipeline generates a versioned compiled object and routes code to target backends. The NumWorks route produces an EADK Rust project for the official tooling.
Editor and tooling
Bring your own editor—or meet the integrated work in progress.
Kalcite already includes VS Code and Zed syntax tooling, plus an LSP crate. The graphical editor exists as a project crate; its public workflow documentation stays carefully scoped while it evolves.
Tooling status
Targets, honestly
Native targets, with explicit delivery status.
NumWorks
Constrained-hardware reference implementation with EADK integration and `.nwa` tooling.
Desktop
A native development runner keeps the same logical 320×240 RGB565 framebuffer.
WebAssembly
The project roadmap names WebAssembly; a web backend is not documented as available.
Kally
An axolotl, a little calcite, and plenty of room to grow.
Kally is the little axolotl who keeps watch over the mineral springs beneath the workshop—collecting useful fragments and helping builders find a clear way forward.
Meet Kally Get started
Start from source, not a sales pitch.
Read the installation notes, run a first program, or inspect the language and compiler reference.