The knee-jerk reaction you are talking about is what is consider by some scholars as an Ontological Functional Constraints [1].
The constraint is considered deadly for the effective exercise of leadership. The constrains can however be removed or at least relaxed in a reliable way. :)
It is a human illness wanting to explain something to just stratify our rational thinking. In reality whenever there is a paradigm shift, the previous explanation becomes obsolete. So stop trying to explain things and go out an do it and experience for yourself.
That's the most common node flow control library, and it's awesome, but it's still built on callbacks. With ES2016 you can have an async function return a value you can assign to with =.
"The most visible difference between React and Mithril is that React's JSX syntax does not run natively in the browser, whereas Mithril's uncompiled templates do. Both can be compiled, but React's compiled code still has function calls for each virtual DOM element; Mithril templates compile into static Javascript data structures.
Another difference is that Mithril, being an MVC framework, rather than a templating engine, provides an auto-redrawing system that is aware of network asynchrony and that can render views efficiently without cluttering application code with redraw calls, and without letting the developer unintentionally bleed out of the MVC pattern.
Note also that, despite having a bigger scope, Mithril has a smaller file size than React."
I'm really interested in mithril from a technology stand point. The thing that holds me back from using it is the ecosphere around it. You look at powerhouses like react and angular and you can find a whole gamut of reusable components that you can just plug and play from the community.
I've been using Mithril a bit, and I like how it's just a library, not a big framework pushing you to use a particular set of components. It's very light and very well documented.
There are these "Mithril" libraries for Bootstrap and Material with 1 contributor and not updated for years, not appearing official at all. In my experience they don't really work.
I'd say it's more in line with Mithril's design to use UI components that are also loosely coupled, like these:
http://topcoat.io/http://purecss.io/
Personally, my ideal library would be one that doesn't make me 'beg for help'... one that is so easy to use that I can just 'weave it in' to all of my existing HTML that need it without needing a mountain of pre made parts to work faster. After all... making strait HTML is pretty damn fast with any competent template engine, server side or client side.
If you want the React semantic without the size, you can just use something like https://github.com/developit/preact (which is like 3kb once deployed).
You also don't need JSX if you don't want to. Using React without JSX and just aliasing the dom functions ends up looking almost the same.
The reason behind React and Flux is because of pitfalls behind MVC...though the whole rational behind that is probably not fit for an hacker news reply :)
The process is more important than the end result.