Why should I use MobX State Tree over vanilla MobX? It seems like any time I read about MobX, MST is mentioned in the same place. Is anyone actually using just MobX by itself?
Probably too general of a question...
Asked
Active
Viewed 4,021 times
15
-
1It's a very broad question and mostly opinion based. MST is good in that it's very opinionated and it's much harder to make bad decisions when structuring your data. MobX on the other hand gives you more freedom to model your data as you see fit, and has less overhead, but it's a lot easier to create data structures that can lead to trouble down the line. I think the easiest way to find out what you like best is to try both approaches. – Tholle Mar 17 '19 at 21:16
5 Answers
28
Actually, MST or MobX State Tree is a very descriptive name if you think about it.
MobX is fast, but doesn't provide any organizational structure out of the box, therefore centralized operations like taking snapshots of the whole state, restoring the state from the snapshot, auto synchronizing separated stores, time travel or hot reloading are either not possible or up to developer to support.
MST supports all of the above mentioned (and more) out of the box by organizing separate stores into a single tree of interactive and interacting nodes.
Central in MST (mobx-state-tree) is the concept of a living tree. The tree consists of mutable, but strictly protected objects enriched with runtime type information. In other words, each tree has a shape (type information) and state (data). From this living tree, immutable, structurally shared, snapshots are automatically generated.
However all of this comes at some cost and MST in general is somewhat slower than pure MobX. So if you do not need those features, do not hesitate to use just MobX.
jayarjo
- 14,000
- 20
- 83
- 123
-
Sorry, I accidentally downvote it. Anyone please upvote for me. Thanks :D – Diamond Jun 30 '19 at 06:59
-
1
-
-
1If you edit(at least one letter) your own answer then I can up-vote instead of down-voting. – Diamond Aug 27 '19 at 07:32
-
-
2
9
Yes, many people use "vanilla" MobX -- it has immense value all by itself. The core concept of leveraging "observable" state is the killer feature of MobX. For me, using it along with React, it has enabled me to fearlessly handle large amounts of connected data in the browser, without worrying about "refresh" issues or "calculated value" issues.
The extra layer of "MST" just adds more (opinionated) structure. ( good if you like being told what to do ;) It is more like a "Redux"-style state manager, where state transitions are clearly defined, and things like time-travel are possible. For me, MobX by itself solves a lot of problems, and I suggest that anyone new should stick to "vanilla" MobX, and not even think about MST until you really appreciate what you are getting from MobX itself.
Nick Perkins
- 7,284
- 6
- 36
- 39
2
I'm not gonna go lengthy comparison.
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. Get comfy to its concepts first, then you decide on your second project :)
Bare MobX is incredibly flexible and can be used very creatively. But you got to understand what you're doing with it. It's a bit like black magic, powerful, but need to be really careful.
hackape
- 11,966
- 1
- 15
- 40
-
1Did you mean to say that? ( if you're new, just use MST ) Don't you mean just use MobX? – Nick Perkins Sep 19 '19 at 20:20
0
I am using MST for react native app. MST references are also very handy to define the data model. I choose MST over mobx for references feature.
Subra M
- 427
- 6
- 15
