Mithril vs. React
Update When starting our web app, we were evaluating different frameworks. We have used AngularJS before and don’t like it, so we were looking something better. We are using React now and it was great, way better than AngularJS.
- Non-standard Promise A+ implementation might be a problem
- Small code base, some basic functionalities require in house extending(e.g. bindonce, skip subtree re-rendering). But I think it is feature complete.
- Routing is too simple, I suspect there will be some pains handling nested views. (e.g. state change hooks, stop state during hooks)
- JSX is non-default, and the syntax might fall behind the latest implementation in React.
- With a minimal API surface, a coding style guide must be followed. On the other hand, React forces some convensions in code. Personally I prefer the Mithril coding style. It does not force a fake OOP style like in React and it should play well with ES6 features.
- A React VS Mithril Comparison
My choice: React.
Therefore, we will keep working with the larger JS community to create a standard for mixins. We will also start designing a new compositional API that will help make common tasks easier to do without mixins. E.g. first-class subscriptions to any kind of Flux store.
Luckily, if you want to keep using mixins, you can just keep using React.createClass.
When working with React, we should favor immutable.