Cheers, Eric, always good to get some insight into transitions like these. While reading, though, I was surprised you didn't mention Mobx-state-tree, which I understand to be better than Redux. I've read this so many times now, it seems like fact (my friend just wrote a Chrome plugin and used this, coincidentally). Have you looked at this at all? If you decided not to use it, could you give some insight?
Here's a couple of links I just googled for anyone who needs a quick overview: reddit.com/r/reactjs/comments/79kn... news.ycombinator.com/item?id=16918675
The reason I didn't mention Mobx is not because I think one is better than the other.
Here is what's important when writing for beginner level audiences. In technologies like React, where I'm trying to advocate for patterns and practices usage, I need to talk about Redux. It's the most widely used and in fact Hooks are directly related to how things are done in Redux. Now my mom has her own fork of Redux, so does Bob down the street, but I didn't mention their forks of Redux.
As well, there is a library called MobX which you mentioned, that is an alternative to Redux, in fact, it's like Redux, but better, I know because you showed me the proof on Reddit.
The average reader especially if not up on all the latest technology will be confused, stressed or maybe even turned off if I mention too many different ways to manage state.
Redux and now hooks are a gateway drug into the state management world. let's let them get their feet wet here and then we will do the "But what else is out there" blog post. As I don't even think I am ready for it yet.
BTW, my mom doesn't really have a fork of Redux. But my friend Bob does. And I hope me being cheeky didn't come off as rude, but I do believe that MobX vs Redux is really a personal or team preference and I feel it complicates an already complicated task of learning the basics of React.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Cheers, Eric, always good to get some insight into transitions like these. While reading, though, I was surprised you didn't mention Mobx-state-tree, which I understand to be better than Redux. I've read this so many times now, it seems like fact (my friend just wrote a Chrome plugin and used this, coincidentally). Have you looked at this at all? If you decided not to use it, could you give some insight?
Here's a couple of links I just googled for anyone who needs a quick overview:
reddit.com/r/reactjs/comments/79kn...
news.ycombinator.com/item?id=16918675
The reason I didn't mention Mobx is not because I think one is better than the other.
Here is what's important when writing for beginner level audiences. In technologies like React, where I'm trying to advocate for patterns and practices usage, I need to talk about Redux. It's the most widely used and in fact Hooks are directly related to how things are done in Redux. Now my mom has her own fork of Redux, so does Bob down the street, but I didn't mention their forks of Redux.
As well, there is a library called MobX which you mentioned, that is an alternative to Redux, in fact, it's like Redux, but better, I know because you showed me the proof on Reddit.
The average reader especially if not up on all the latest technology will be confused, stressed or maybe even turned off if I mention too many different ways to manage state.
Redux and now hooks are a gateway drug into the state management world. let's let them get their feet wet here and then we will do the "But what else is out there" blog post. As I don't even think I am ready for it yet.
BTW, my mom doesn't really have a fork of Redux. But my friend Bob does. And I hope me being cheeky didn't come off as rude, but I do believe that MobX vs Redux is really a personal or team preference and I feel it complicates an already complicated task of learning the basics of React.