I really wish Redux hadn't fallen out of favor so dramatically. In my experience a large proportion of the problems people ran into stemmed from the fact that t

I really wish Redux hadn't fallen out of favor so dramatically. In my experience a large proportion of the problems people ran into stemmed from the fact that the elegantly architected, unidirectional data flow model often had to mate with HTTP/REST backends, which fundamentally force you into a request/response model. This results in a combinatorial explosion of states and transitions you have to care about with respect to "in-flight", "error", "canceled", "received", etc. parts of the request/response lifecycle. The other issues people had like boilerplate and massive reducer files I think were solvable with various conventions or tools, but forcing an interface between unidirectional data and request-response seemed like an intractable problem. I've wondered for awhile if there could have been some way of extending the unidirectional flow all the way back to the server in a way that could solve this mismatch in a cleaner manner.