[MsMowz]

The problem is I always end up writing a state container that's similar to redux at some point if I don't use it. For simple things, you don't need a state container, but where is the line between simple and complex? It's hard to tell, and since redux is so low overhead, why not err on the side of using it now if you think there's a chance you'll want to later?

[ngsayjoe]

The key here is end up if you project too much into the future then it is premature optimization. I might end up becoming the next Google let's write our back-end in C++.