THE ZLANG OBSERVATORY
A language taking shape.
Streaming by nature. Responsive by design.
An independent language for fast applications and first-class zui.
Loading checkpoint…
Published snapshots · refreshes every 60sOn the workbench
IN PROGRESSLoading current work…
Browse checkpoint ↗PERFORMANCE LAB
Less work. Measured honestly.
Explore the cost of state updates, then compare generated code with Rust. Every result keeps its scope and source checkpoint.
One service. Different subscriptions.
How broad and granular invalidation trade CPU for memory.
Loading workload…
Update CPU
ns / frameMedian ± median absolute deviation
Retained heap
KiB · requested live Rust allocation bytes
Rust callbacks and native state tracking. Excludes GPUI rendering, Text, I/O and Zeron. This compares policies, not zlang against Rust.
All 8 workloads & measurement details
Making bursts cheaper
Before & after · skip subscriber walks when every view is already dirty
MEASURED CHANGE
No extra tracking metadata. One clean unrelated view disables this global shortcut; it does not solve general subtree rendering.
Refresh the mounts that changed
Two measured steps · coalesced wakes, then fewer child synchronization passes
Refresh CPU
µs / frameMedian ± MAD · not a confidence interval
Retained setup heap
KiBRequested live Rust bytes · not RSS
Actual mounted-tree adapter and native bindings. Mixed build profile: adapter/native/runtime optimized; other dependencies use the dev profile. Excludes GPUI layout, paint and whole-application performance. Comparisons were timed separately; do not multiply stage ratios.
All 31 workloads & source checkpoints
The cost of subtree caching
Experimental component rendering · direct renderer stays the default
Frame CPU
ms / requested frameMemory cost
Excluded failure: 64 children with changing font size produced different button geometry. Negative-position rounding needs a correctness fix; increasing cache capacity cannot repair it. Raw evidence includes this failure and the ordinary snapshot renderer.
zlang × Rust
Checkpoint microbenchmarks · time & allocations
Overall Rust parity remains open. Small UI differences are within measurement noise; these results do not measure a complete application.
Source provenance & limitations
THE ROAD AHEAD
A clear view of the work.
Tracked tasks, not a language completion percentage. The list grows as implementation and testing expose more work.
Language foundations
EVIDENCE, NOT ASSUMPTIONS
Built. Tested. Still being verified.
Passing tests cover the implemented subset. Whole-language Rust-equivalent safety and application performance remain unverified.
CHECKPOINT LOG