Examples

These examples are meant to make TKO’s model visible.

• They focus on observables, bindings, and update locality.
• They are intentionally interactive.
• They are self-contained HTML files you can inspect, copy, or adapt directly.
• They are designed to show what work is happening, not just what UI appears.

Available examples

• Honeycomb: Count naive virtual DOM comparisons against observable updates in a dense interactive field.
• odoom: A tiny WebGL corridor crawler where the HUD, controls, and simulation state stay observable-driven.
• Spreadsheet: Cells as observables, formulas as computeds, and dependency propagation you can edit live.
• Signal Graph: Mutate one input and watch only the downstream computed branch recompute.
• Form Engine: A realistic product form showing dirty state, validation, summaries, and save flow as reactive state.

Why this section exists

TKO often feels different from virtual DOM frameworks because it connects observable state directly to DOM updates.

That difference is easier to understand when you can interact with it and watch the cost accumulate.