En bref, MobX is unopinionated util lib , while MST is an opinionated solution built on top of MobX. If you’re new to MobX, just use MST.
Read moreWhy you should not use MobX?
MobX does not provide any restrictions on how new states can be derived from old ones . It’s more of a Data flow library as its creator likes to call it. MobX helps us set up Reactivity outside React components. This way view components can be kept free of logic.
Read moreWhat is MobX state tree?
What is MobX-State-Tree? Technically speaking, MobX-State-Tree (also known as MST) is a state container system built on MobX, a functional reactive state library . This may not mean much to you, and that’s okay.
Read moreHow big is MobX?
The gzipped minified build size dropped from 17.3kB to 14.2kB (22% smaller). But, in practice this will shave off even a bit more, as MobX 4 is better tree-shake-able.
Read moreWho created MobX?
One of the most interesting quotes I’ve found from Michel Weststrate (the founder of MobX): Reacting to state changes is always better then acting on state changes.
Read moreHow does MobX state tree work?
The tree consists of mutable, but strictly protected objects enriched with run-time type information . In other words; each tree has a shape (type information) and state (data). From this living tree, immutable and structurally shared snapshots are generated automatically.
Read moreWhat is MobX state?
mobx-state-tree (also known as “MST”) is a state container that combines the simplicity and ease of mutable data with the traceability of immutable data and the reactiveness and performance of observable data .
Read more