60% is a mighty big number, no?
-
-
Replying to @wycats @ryanflorence
to be fair, React's state management can be clunky for many. There's literally no use case I wouldn't rather use MobX
1 reply 0 retweets 7 likes -
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 …
2 replies 1 retweet 4 likes -
Replying to @AdamRackis @wycats
yeah, I don't like the assignment style of state changes, hard to find out who changed what.
1 reply 0 retweets 4 likes -
Replying to @ryanflorence @wycats
that is true - you trade a much simpler model, for less explicitness / more magic.
1 reply 0 retweets 0 likes -
Replying to @AdamRackis
I've had enough magic in my career. Pass a prop, I can follow that in a call stack if I need to.
1 reply 0 retweets 8 likes -
Replying to @ryanflorence @AdamRackis
so you prefer synchronous updates?
2 replies 0 retweets 0 likes -
Replying to @wycats @AdamRackis
This doesn't answer "who changed state" but "where'd it come from", so not talking about updates here.
2 replies 0 retweets 0 likes -
Replying to @ryanflorence @AdamRackis
what's your primary critique of mobx?
1 reply 0 retweets 1 like -
Replying to @wycats @AdamRackis
I actually think its perfect for the kind of app it was born from: spreadsheets. The spreadsheet model is great for lots of derived values.
2 replies 0 retweets 6 likes
aren't derived values just the opposite of pushing state down?
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.