The overcomplication (relative to what could be) is due to boilerplate and poorly defined convention for anything but the canonical todo app. It's early days.

The overcomplication (relative to what could be) is due to boilerplate and poorly defined convention for anything but the canonical todo app. It's early days. There are some frameworks using some form of the Flux spec like Fluxxor and Reflux, but they're not opinionated or complete enough to hit the ground running. The author of Fluxxor, for example, is himself working out where to put very basic functionality like network service calls. In the react-router project, there's not an obvious way to either render from server or refetch data on route changes. This is all very basic functionality for a medium to large project. It will feel like you're in the weeds after a couple of days of development. We need a Flux++ framework with some stronger opinions, closer to Ember or Angular in scope.