Thursday 15th September, 2016
2:10pm to 2:55pm
Have you ever noticed that component state seems to appear at *just* the right spot to make component re-use painful? You're not alone, and thats why Redux exists. It solves the problem by putting all your state outside the app. And then creates two new problems -- structuring it and *getting it back where you need it*. So basically, state is painful. Redux is painful. *Picking between state and Redux is painful.* But what if we just avoided it all in the first place?
Sign in to add slides, notes or videos to this session