The Flux Challenge is "tailored to touch Flux's weakest spots", especially "coordinating multiple async data sources", so Flux solutions are sought, but other a

The Flux Challenge is "tailored to touch Flux's weakest spots", especially "coordinating multiple async data sources", so Flux solutions are sought, but other approaches to state management are welcome. The Challenge author used his own reactive framework and RxJS: https://cycle.js.org/ https://cycle.js.org/ https://github.com/Reactive-Extensions/RxJS https://github.com/Reactive-Extensions/RxJS My solution leverages my Matrix data flow library (versions in Common Lisp, CLJ/S, and JS). Matrix is much like the JS MobX, if you know that. https://github.com/kennytilton/matrix https://github.com/kennytilton/matrix https://mobx.js.org/index.html https://mobx.js.org/index.html Moral: The data flow paradigm is well-suited to smoothly absorbing external input, so the async feeds of the Flux Challenge are right in the data flow wheelhouse.