Skip to content

Commit eb162a6

Browse files
authored
Update reactivity-in-depth.md (#2246)
1 parent 55fafe7 commit eb162a6

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/guide/extras/reactivity-in-depth.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -407,7 +407,7 @@ Quite a few other frameworks have introduced reactivity primitives similar to re
407407
- [Preact Signals](https://preactjs.com/guide/v10/signals/)
408408
- [Qwik Signals](https://qwik.builder.io/docs/components/state/#usesignal)
409409

410-
Fundamentally, signals are the same kind of reactivity primitive as Vue refs. It's a value container that provides dependency tracking on access, and side-effect triggering on mutation. This reactivity-primitive-based paradigm isn't a particularly new concept in the frontend world: it dates back to implementations like [Knockout observables](https://knockoutjs.com/documentation/observables.html) and [Meteor Tracker](https://docs.meteor.com/api/tracker.html) from more than a decade ago. Vue Options API the React state management library [MobX](https://mobx.js.org/) are also based on the same principles, but hide the primitives behind object properties.
410+
Fundamentally, signals are the same kind of reactivity primitive as Vue refs. It's a value container that provides dependency tracking on access, and side-effect triggering on mutation. This reactivity-primitive-based paradigm isn't a particularly new concept in the frontend world: it dates back to implementations like [Knockout observables](https://knockoutjs.com/documentation/observables.html) and [Meteor Tracker](https://docs.meteor.com/api/tracker.html) from more than a decade ago. Vue Options API and the React state management library [MobX](https://mobx.js.org/) are also based on the same principles, but hide the primitives behind object properties.
411411

412412
Although not a necessary trait for something to qualify as signals, today the concept is often discussed alongside the rendering model where updates are performed through fine-grained subscriptions. Due to the use of Virtual DOM, Vue currently [relies on compilers to achieve similar optimizations](https://vuejs.org/guide/extras/rendering-mechanism.html#compiler-informed-virtual-dom). However, we are also exploring a new Solid-inspired compilation strategy (Vapor Mode) that does not rely on Virtual DOM and takes more advantage of Vue's built-in reactivity system.
413413

0 commit comments

Comments
 (0)