01 Depth
"What is the smallest change I can make that still triggers updates?"
ShallowDeep
JavaScript only sees a write when it goes through a setter or Proxy trap. Mutate a nested object and the
outer reference never notices. That's why primitives get wrapped in a container with .value, and
why deep systems (Vue, MobX, Solid stores) recursively proxy everything you touch.
Shallow is simple and leans on reassignment. Deep is ergonomic but brings proxy identity weirdness.
Either way, every system ships an escape hatch: requestUpdate(), triggerRef(), notify().
Read Part 2: Deep vs. Shallow →
02 Granularity
"At what level are changes detected, and how does the system find what actually changed?"
CoarseFine
Scope shrinks in rings: window, application, service, component, template, DOM node. Zone.js rechecks
the world. React re-renders a subtree and diffs. Signals frameworks track every read and update the exact
bound node.
Coarse is simpler and gets you surprisingly far. Fine does less work, but now you own dependency
tracking: de-duping, conditional reads, and the diamond problem.
Read Part 3: Coarse vs. Fine →
03 Directionality
"Does change get pushed to dependents, or pulled at render time?"
PullPush
Every framework nudges itself on a write, so that's not the test. A system is push when its
dependencies are figured out ahead of time. Pull systems re-run render top to bottom and
never see an inconsistent state.
Push-pull (signals) must solve glitches with scheduling and topological ordering. There's no truly pure
push framework; Svelte 4 comes closest.
Read Part 4: Push vs. Pull →