Still early days for Flux, but the principles are sound and I hope it offers a viable alternative to all these framework that rely mainly on variants of the MVC pattern.
For another overview, see this article:
http://blog.andrewray.me/reactjs-for-stupid-people/
Please don't take offence at the title, I didn't write it :D
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.
About Mithril, HTML generation with JavaScript is an odd design choice. Obviously it's much better from a technical point of view, but nested or complex HTML must get ugly fast, and I really don't want to deal with template code written by non-developers. Having said that, for a certain class of apps with high performance requirements and comprehensive browser support, Mithril is a very appealing option.
That's the problem JSX solves - nesting tags and attributes is less syntactically onerous than managing a tree of function calls or nested object structures, with their attendant braces and commas.
Here's the Mithril getting started example [1] done using JSX [2], for comparison (some of the other code has changed since I did this, but the rendering part looks the same)
[1] http://lhorie.github.io/mithril/getting-started.html#summary [2] https://github.com/insin/msx/blob/master/test/jsx/example.js...