4 ms·
MobX is quite popular, and I wouldn't call it a variant of redux. Also, just storing state in your higher level components can work for much more complicated a
by bryanlarsen 10y ago
MobX is quite popular, and I wouldn't call it a variant of redux.
Also, just storing state in your higher level components can work for much more complicated apps than many think.
- mercer 10y agoI've done the latter and even though it's possible, it gets tedious/unproductive pretty quickly. To elaborate: in 'response' to the webdev tendency I have to use the latest and greatest, and the HN articles about this phenomenon, I've done a few React projects with a conservative mindset. React-router I don't miss too much for much of it. I could also do without a bunch of ES6/7 features, TypeScript, and so on. But with each of these projects I wish I'd used Redux, MobX, Baobab, and so on instead of the 'vanilla' approach of keeping state in my higher level components. tl;dr: if you're gonna be conservative, leave state management as the last thing you 'conserve' on.
- samsonradu 10y agoThis is so true. Just apply the Redux idea of smart/dumb components but without actually using Redux. Higher level component(s) becomes smart and handles the state changes while passing down only properties to children. Usually I start an app like this and when things get really complicated I add Redux and refactor the state management out of my top component. MobX looks interesting, however didn't get to try it out yet, only briefly looked over it. I find it a bit annoying that they introduce even more syntax overloading - annotations - as if ES6/7/JSX is not enough already. Will give it a try on a pet project soon.
- charrondev 10y agoTo be fair they give many examples of using mobx without decorators. I use them because they're baked into typescript, but I wouldn't use the Babel plugin, it seems less mature.