No flame wars please - honestly curious where the React community is these days. For new Pr/React projects, I use ___ for state management.
-
-
It's strange. At
#reactconf the creator of react was asking people this same question, if they said "component state" he'd high five them. -
There's a weird idea that "react doesn't provide state management" when that's like ... one of the two things it does

-
60% is a mighty big number, no?
-
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.
- 5 more replies
New conversation -
-
-
gotta write a bunch of weird code when people want the illusion that they own state that isn't theirs! I'm a pragmatist, not a scientist.
-
if 60% of people use redux, justified or not, in order for the router to be successful we have to appease them.
-
We can be "right" or we can be useful. I'd pick useful every time.
-
there is no answer to which library is the right answer I prefer MobX but apparently I'm minority.
-
I'm split, honestly. I could happily use either. Currently on MobX at work, Redux on side - both great
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.