When building software, and shipping it to the world you might find yourself asking an array of questions. How will you measure usage? Will you know how users are using it once it’s launched? What about user authentication? You’ll definitely want to track that, but how will you do it?
With a redux style architecture, the answers to those questions are even more obfuscated. Josh Habdas gives us a deeper look at how he solved this problem for his team.
In front end development it's easy to get into a tribal mindset, and to demean tools that are different than the tools we use; it's easy to do, but not very productive.
Emmanuel Luciano gives us a first hand look at how he experienced changing tools and what value you can find by exploring what other libraries or frameworks can offer.
To a lot of web developers, Flux was an entirely foreign paradigm, and since Flux was more of an idea than an actual implementation we ended up buried in different Flux libraries. Most of them attempted to handle Flux the same way, with small variations.
Then came Redux, the Flux library to end them all. Redux introduced a much saner approach to Flux, and offered some really great tools like time traveling debugging. Daiwei Lu gives us his experience with Redux and how we can apply the lessons he learned in other platforms.