Redux: Simplifying Application State in JavaScript




Tim Griesser

As JavaScript applications increase in complexity, consistent patterns for managing state becomes considerably more important, and difficult to achieve without good patterns.

Redux is a library which provides a “Predictable state container for JavaScript apps”. Utilizing proven patterns from more functional languages, Redux is a framework agnostic library which combines convention with functional approaches. In this talk we will take a look at Redux, Redux middleware, and how it can be used to track data flow and state changing over time, producing applications which are easier to develop and debug.

We will also take a look at some of the similarities and differences of Redux vs. other libraries, frameworks, and tradeoffs that exist compared to existing approaches to solving these problems.

Original source


10 responses to “Redux: Simplifying Application State in JavaScript”

  1. I've seen switch statements being used in all the different Redux videos and tutorials for the core logic of the reducer. Wouldn't something like a Map make sense to fetch the actual reducer associated with the action type? I'm wondering cause it makes more sense to me, yet the prevalence of the pattern across all examples I've seen, provided by all kinds of brilliant people all use that same switch/case pattern.

  2. I thought premature optimization was the root of all evil? Maybe evil has more than root, but I've come to like a single source of truth. I'm going to go with { evil: ["premature optimization", "state", "computers, because they do what I say, not what I mean"] }.

  3. Everything was fine until you said that RxJS doesn't make sense to you. That's why you prefer Redux framework only because you don't understand the simple concept of add Observer and Iterator patterns together.

Leave a Reply