I know that a lot of people have complained about the "boilerplate" that Redux involves, but as Dan Abramov said in "You Might Not Need Redux" [0], there's tradeoffs involved. Redux asks that you write your code with some constraints, and those constraints in turn open up some interesting possibilities. Time-travel debugging is one of them. May not be useful for _every_ scenario, but I've certainly found it incredibly helpful in my own app. @mdiordiev has done a fantastic job taking the DevTools core that Dan built and the Monitor UIs built by the community, and wrapping those up into a cohesive tool that makes the debugging experience even better.

For anyone out there looking to get started with Redux, I keep a big list of links to high-quality tutorials, articles, and resources for React, Redux, and related topics [1] - specifically intended as a great starting point for anyone trying to learn the ecosystem, and a reference for more advanced techniques and topics. I also have a catalog of Redux-related addons and utilities as well [2].

[0] https://medium.com/@dan_abramov/you-might-not-need-redux-be4...

[1] https://github.com/markerikson/react-redux-links

[2] https://github.com/markerikson/redux-ecosystem-links