Mobx-state-tree: Opinionated, transactional, MobX-powered state container

See https://github.com/mobxjs/mobx/issues/681#issuecomment-26234... (that thread started only yesterday, so it isn't very long yet), but yes, MobX is in use in large complex production apps for a long time.

For example in proppy.io, as described here: https://blog.wearewizards.io/a-mobx-introduction-and-case-st...

I've been transitioning goskive.com from alt.js to mobx for the past half year or so. The reason it's taking a long time is I'm doing it incrementally. If there's a store that needs to change for a feature then I convert it to mobx.

I've got nothing but praise for Mobx. So far the only feature I'm missing is observable Sets.

I was using Immutable.JS with alt.js and ended up writing a lot of boilerplate. While I sometimes miss the API from Immutable.JS, the simplicity of working with mobx more than makes up for the lackluster API of vanilla JS data structures.

Admittedly there's very little high performance stuff we do, although our study mode with moving questions/flashcards has had poor performance previously and I had to optimize parts of it.

Happy to answer any questions you might have. FWIW I've never worked on an app with Redux.

We're using MobX and React for nuclino.com and for us it has scaled very well for something which is much more than just a todo list app. We're very focused on performance and creating a snappy experience and so far we didn't have to do much performance tuning that was specific to MobX. Happy to answer any more specific questions.