Deep Dive: Reactive 'Tale of Two Systems' (Refs vs. Reactive Objects)

ref creates an object with a .value property to track changes; reactive uses Proxies to track changes to object properties directly.

Architecturally, ref is the recommended default for most state because it works for all data types (primitives and objects) and makes 'reactivity' explicit via the .value property. reactive is powerful for collections of data but has 'gotchas': you cannot destructure a reactive object without losing reactivity, and you cannot replace the entire object (e.g., state = newObject). ref handles replacement seamlessly via state.value = newObject.