No flame wars please - honestly curious where the React community is these days. For new Pr/React projects, I use ___ for state management.
-
-
to be fair, React's state management can be clunky for many. There's literally no use case I wouldn't rather use MobX
-
How I explained MobX: "you'd think this code would work: add these decorators and it will." https://github.com/arackaf/okc-mobx-lightning-talk/blob/6c182766fe17ebe6ce847efef8d94be02c4f267b/app/component.es6 …
-
yeah, I don't like the assignment style of state changes, hard to find out who changed what.
-
that is true - you trade a much simpler model, for less explicitness / more magic.
-
I've had enough magic in my career. Pass a prop, I can follow that in a call stack if I need to.
-
so you prefer synchronous updates?
-
This doesn't answer "who changed state" but "where'd it come from", so not talking about updates here.
-
what's your primary critique of mobx?
- 2 more replies
New conversation -
-
-
Yep. I'm still baffled by it. I blame flux. Made everybody think components can't hack it.
-
I mean, redux is really neat. It's just the big number of people who show up to our advanced workshops who think setState is an antipattern.
-
If setState is an antipattern, how does redux work?
-
dispatch -> reduce actions to value -> forceUpdate
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
