2 ms·
With context api and hooks you don't need redux or mobx. Not that either one was really all that necessary in the first place anyway.
by supermw 8y ago
With context api and hooks you don't need redux or mobx.
Not that either one was really all that necessary in the first place anyway.
- _coveredInBees 8y agoI've still found the concept of computed properties in mobx to be extremely useful (and I say this as someone who relies on regular React + SetState 90% of the times). MobX encourages you to think about representing your state in the minimal possible representation and to heavily use computed properties that depend on this smallest, irreducible state representation for everything else. Switching to this mindset makes developing more complex components (especially UI/forms) a breeze. I also find MobX to be great for async things and much easier to handle than via setState. Using setState alone in these types of complex components ends up being really tedious and prone to errors (largely driven by the async nature of setState updates).