Tag:signals
All the posts with the tag "signals".
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.
backbone-signal - Practical Reactive Programming in Javascript
Introducing backbone-signal, which adds Signals to Backbonejs.
My history with reactive state management & how I ended up using ctx-core & nanostores
A brief account of my history with state management & the road to building ctx-core & adopting nanostores
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.
Signals Proposal Compared to rmemo/WeakRef
WeakRef can simplify systems built using the Signals Proposal. By removing the need to unwatch live Signals. WeakRef is criticized for having extra memory allocations & being slow.
This post shows benchmarks. Including the Signals Proposal polyfill & rmemo, a reactive library that uses WeakRef. Comparing:
- performance
- memory usage
- implementation
V8 & Javascript Core have different Garbage Collection behavior for WeakRef. This caused me confusion with my initial benchmarks which were only synchronous. This post demonstrates the implementations. This post then highlights use cases where WeakRef can be used for simple & flexible reactive apis.