Where Krypton stands today vs the other native and systems-targeting languages, dimension by dimension. We're transparent about both shipped capabilities and known gaps.
✓ supported ◎ partial − not in this language … on the Krypton roadmap
| Dimension | C | C++ | Odin | JS | Swift | Obj-C | Krypton |
|---|---|---|---|---|---|---|---|
| Direct native code | ✓ | ✓ | ✓ | − | ✓ | ✓ | ✓ |
| No LLVM dependency | ✓ | − | − | ✓ | − | − | ✓ |
| Manual memory | ✓ | ✓ | ✓ | − | ◎ | ◎ | ◎ |
| Garbage collection | − | − | − | ✓ | ✓ | ✓ | ✓ |
| Generics / templates | − | ✓ | ✓ | ◎ | ✓ | − | … |
| Async / concurrency | ◎ | ◎ | ◎ | ✓ | ✓ | ◎ | … |
| Native threads | ◎ | ✓ | ✓ | ◎ | ✓ | ✓ | … |
| Closures | − | ✓ | ✓ | ✓ | ✓ | ◎ | ✓ |
| Standard collections | − | ✓ | ✓ | ✓ | ✓ | ✓ | ◎ |
| Package manager | − | ◎ | − | ✓ | ✓ | − | … |
| Native macOS UI | ◎ | ◎ | ◎ | − | ✓ | ✓ | ◎ |
| Native Windows UI | ◎ | ◎ | ◎ | − | − | − | ✓ |
| Browser target (WASM) | − | ✓ | ✓ | ✓ | ◎ | − | ✓ |
| HTTP server (in stdlib) | − | − | − | ✓ | ✓ | − | ✓ |
| Language server (LSP) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Compiler written in itself | − | − | ✓ | − | − | − | ✓ |
| Ecosystem maturity | ✓ | ✓ | ◎ | ✓ | ✓ | ✓ | − |
Krypton's design goal is native machine code, no LLVM, no clang on every platform — same target as C and Odin, with the safety net of mark-sweep GC and closures.
The four … cells are the gaps we're actively working through: generics, threads, async, and a package manager. The roadmap entries below sketch the order they land in.
stdlib/fp.k functional core.*u8, *Vec3) for raw-byte / struct-field fast paths.kcc is written in Krypton.k:server_native) with zero C / zero clang.k:choc, in flight).k:gui, 98 widgets shipped).krSpawn / krJoin + atomic ops — native threads on Windows (CreateThread), POSIX (pthread_create). Q3 2026.func map[T](xs: [*T], f: (T) -> T). Q4 2026.krpm package manager + central registry. Q4 2026.k:choc so a single .ks source can target a desktop app, a CLI, and a browser page. 2027.Honest take: Krypton's already credible for embedded/systems work and CLI tools. The competition story for app development on every platform is 12-18 months out. The fundamentals (small core, native everywhere, no LLVM) are sound; the gaps are concurrency, generics, and ecosystem.