Who created 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.

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.

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 .

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.

Ten reasons you should use MobX-State-Tree: Your data is mutable, but can only be mutated in “actions”, so it’s easy to use but also protected. Via runtime type checking, you can’t accidentally assign the wrong data type to a property. TypeScript can infer static types from your runtime types automatically.

How MobX and MobX State Tree are different: Opinionated — MobX State Tree is very opinionated on how data should be structured and updated, while MobX allows you to structure your data and actions however you would like .30 Oca 2018