Tag:reactive-signals
All the posts with the tag "reactive-signals".
Slot → Cell → Signal: Composing Lazy and Eager Reactivity in One Graph
How lazily-rs composes three primitives — Cell, Slot, and Signal — so you can pick lazy (compute-on-read) or eager (recompute-on-change, no unset window) per derived value inside a single dependency graph. With use cases and diagrams.
Reactive State Machines: How lazily-rs Drives agent-doc's Cycle State
A finite state machine shouldn't be a pile of scattered if-checks. This post shows how lazily-rs's StateMachine primitive — a Cell-backed FSM with a pure transition function and reactive observers — became the single transition authority for agent-doc's per-document cycle state, replacing ad-hoc phase guards with one declared table. With diagrams of the phase graph, the FSM-plus-durable-journal architecture, and how the same reactive graph that runs your UI can run your protocol.
Lazily: Reactive Primitives Done Right — Context, Slots, Cells, and Signals
Introducing lazily — a multi-language reactive primitives library (Rust, Zig, Python) built on lazy invalidation. Deep dive into Context, Slot, Cell, and Signal abstractions, lazy vs eager reactivity, and how proper hydration (code and body) eliminates waste.
The lazily Architecture: One Reactive Graph from Local Memory to the Network
A full-architecture tour of lazily — the reactive core (Context, Cell, Slot, Signal, Effect), the three execution contexts (single-threaded, thread-safe, async), the Snapshot/Delta wire protocol that carries the same graph state across IPC, WebSocket, WebRTC, and FFI, and the cross-language family. With use cases and diagrams.
A Spreadsheet at Google-Sheets Scale: Cell Families and Focused Recompute in lazily-rs
lazily-rs now backs a full-capacity Google Sheets workbook — 10,000,000 cells — and the part that matters isn't the build time, it's that editing one cell and reading a 1,000-cell viewport costs ~11 microseconds no matter how big the sheet is. This post walks through the two new keyed primitives that make it possible — CellMap and CellFamily — and the lazy pull-based model that recomputes only the cells you focus on, with diagrams of coarse-vs-fine-grained reactivity and the spreadsheet graph.
Eight Implementations, One Spec: Redundancy as an Epistemic Device
Building the same reactive library in eight languages against a shared normative spec, a Lean model, and a load-test harness ... and what that combination found that no single implementation could. Why six normative clauses accumulating around one primitive meant the primitive was wrong, which is also the honest answer to 'isn't a reactive just an observer?'. Five ways a conformance suite reports green while checking nothing. Benchmarks that lied by 2x on a busy workstation.
Signal Is Not a Reactive Primitive
Signal is a composition of a memoized slot and a puller effect... five lines, in every binding. The frontend ecosystem promoted it to a primitive, and the TC39 proposal quietly didn't. Plus: why weak back-edges are an ergonomics driver before a performance one, what non-GC languages pay instead, and how naming ambiguities are a reliable way to find architecture bugs.