3 ms·
If you started with React a few years ago, then React would have been brand spanking new, so change shouldn't have been too surprising then. The question is, h
by bryanlarsen 10y ago
If you started with React a few years ago, then React would have been brand spanking new, so change shouldn't have been too surprising then.
The question is, have things stabilized now? There's some evidence it has: Redux & Webpack have had the mindshare for almost 2 years now. But a lot of people now recommend mobx over redux, the redux plugin situation is still evolving, react-router seems to have finally got things right with version 4, et cetera.
That being said, I think the above sounds more pessimistic than it really is. For example, redux vs mobx is really two different use cases IMO.
- acemarke 10y agoWhen you say "Redux plugin system", what specifically are you referring to?
- eyko 10y agoI imagine packages that bridge react components with redux (react-redux, react-router-redux, redux-forms, redux-immutable). But I'm not sure to be honest.
- deleted 10y ago[deleted]
- Swizec 10y ago> For example, redux vs mobx is really two different use cases IMO. I wouldn't go that far, I'd say it's different ways of thinking about the same problem. Crucially, switching out your Redux stores/sagas for MobX stores should be a drop-in replacement for the most part. Actions are still actions, and stores are still stores. The only/main difference is that for MobX a reducer and an action are the same thing.
- kimshibal 10y agonice, can't wait to replace mobx with something new next year