JavaScript Reactivity, the one-pager
Every framework, plotted on three axes
Parts 1 to 4 on one page.
Depth and granularity describe how a change is noticed . Directionality describes how the
view updates .
The three axes
01 Depth
"What's the smallest change that triggers an update?"
Shallow Deep
JavaScript only sees writes through a setter or Proxy. Nested mutations go unnoticed unless you wrap the
value (.value) or proxy everything (Vue, MobX, Solid stores).
Shallow is simple; reassign to update. Deep is ergonomic, with proxy identity weirdness. Everyone ships an
escape hatch: requestUpdate(), triggerRef(), notify().
Read Part 2: Deep vs. Shallow →
02 Granularity
"How narrowly is a change detected?"
Coarse Fine
Anywhere from the whole window down to one DOM node. Zone.js rechecks everything, React diffs a subtree,
signals update the exact node.
Coarse is simple and goes far. Fine does less work, but you own dependency tracking and the diamond problem.
Read Part 3: Coarse vs. Fine →
03 Directionality
"Is change pushed to dependents, or pulled at render?"
Pull Push
Push means dependencies are known ahead of time . Pull re-runs render top to bottom and
never sees inconsistent state.
Push-pull (signals) needs scheduling to avoid glitches. Nothing is pure push; Svelte 4 comes closest.
Read Part 4: Push vs. Pull →
Four families emerge
Depth crossed with granularity.
Interactive chart in Part 1.
Fine + deep
Reactive graphs
Proxies track exactly which paths you read. Vue, MobX, Valtio, Solid stores, Svelte 5.
Fine + shallow
Atomic primitives
A box around a value. Signals, shallowRef, nanostores.
Coarse + shallow
Diffing
Swap the reference, re-render, compare. React, Preact, Redux, Lit.
Coarse + deep
Wholesale discovery
"Something changed, go find it." Slowest, easiest to share. Zone.js, wc-services.
Where each one lands
All
Pull
Push-pull
Push
The takeaways
Detection and response are separate. Re-rendering everything doesn't make a system deep.
Part 2 →
Every system has an escape hatch, usually reassigning the top-level reference.
Part 2 →
Fine-grained frameworks converge. Read to subscribe, write to notify. Only the API spelling differs.
Part 3 →
The diamond problem decides push vs. pull. Pre-wired dependencies need topological
ordering. Pull dodges it.
Part 4 →