What about Mithril? It's tiny, efficient and predates React. Here is a good overview of it: <a href="https://lhorie.github.io/mithril/comparison.html" rel="nofollow">https://lhorie.github.io/mithril/comparison.html</a>
Elm [1] is also worth looking into. I've been using it of late and having fun with it, despite some quirks. It's quite performant in practice too. Though I haven't done comparisons myself, Elm benchmarks claim it to be the fastest only next to Mercury [2].<p>[1] <a href="http://elm-lang.org" rel="nofollow">http://elm-lang.org</a>
[2] <a href="http://elm-lang.org/blog/Blazing-Fast-Html.elm" rel="nofollow">http://elm-lang.org/blog/Blazing-Fast-Html.elm</a>
Nice. I've used ractive for nearly two years now. It's backed by the Guardian and you can learn it by reading this comment:<p><pre><code> var binding = new Ractive{
el: '.where-to-put-it',
data: {some: data},
template: '<p>Put {{ some }} thing here</p>'
}
</code></pre>
Bang, two way binding, virtual DOM, and ridiculously fast when using the same benchmarks that ember and react use to test their performance.
I'd go with Facebook and the consequent support, testing and community over a framework that does it's own thing. Performance is simply not a concern for most applications (i.e. React itself is more than good enough) and having learned React to a good standard, I'm super excited about building something in React Native.
I recently came across Arch, a compelling functional style approach to React using LiveScript with a central immutable state architecture inspired by Om.<p>- <a href="https://github.com/redbadger/arch/tree/master/docs" rel="nofollow">https://github.com/redbadger/arch/tree/master/docs</a><p>- <a href="http://www.slideshare.net/LondonReact/react-london-april" rel="nofollow">http://www.slideshare.net/LondonReact/react-london-april</a>
Anyone with experience with either/both Morearty.js and Omniscient.js care to explain the differences between the two?<p>From what I could gather with a quick look, they seem almost identical in terms of features and scope.<p><a href="https://github.com/moreartyjs/moreartyjs" rel="nofollow">https://github.com/moreartyjs/moreartyjs</a><p><a href="https://github.com/omniscientjs/omniscient" rel="nofollow">https://github.com/omniscientjs/omniscient</a>
>Essentially any event where the user would expect feedback means you need write the conditional structure in the output. So if the user types a character in an input box then you need to write the value of the input box to be the characters the user has typed so far<p>Anyone able to provide a quick description of what this means?
Is ReactJS (the virtual DOM) considered a 'reactive framework' but 'reactive programming' something else entirely? <a href="https://gist.github.com/staltz/868e7e9bc2a7b8c1f754" rel="nofollow">https://gist.github.com/staltz/868e7e9bc2a7b8c1f754</a>
Nice comparison. Didn't anybody think of implementing a react-like framework in CoffeeScript? There is a coffee-react library tool, but I feel like the ideas of react implemented natively for CoffeeScript would be a match made in heaven...
This is a really nice overview of the status quo.<p>It's also great to see a statement on JS lib proliferation which lays out a concise, balanced and pragmatic argument.