elm-html

This is such a superficial aspect of the framework that it's really not worth discussing. You need to go deeper to learn it properly, and only then give verdict. In ClojureScript (Om, Reagent, etc), you have the same HTML building pieces with code. Also in Elm you use normal Elm functions, not a HTMLish DSL. Also, nowadays in Cycle.js we use the more friendly syntax: .map(name => div([ label('Name:'), input('.field', {attributes: {type: 'text'}}), h1('Hello ' + name) ]) ) Which was inspired by elm-html https://github.com/evancz/elm-html .

To explain why this is nicer than react: virtual-dom makes zero to non assumptions about your architecture. which I like. It's just dumbly a diffing algorithm and that's it. Mercury[0] is a "framework" (A collection of opinionated modules) that builds on top of this to give a more complete app stack. And it's really fast[1]. Because it's so dead simple and takes so little assumption, it's really easy to mold to your needs. For example, we've chosen to use it for our Haskell virtual-dom implementation[2]. Also Elm has chosen to use this library for their `elm-html` library [3] and PureScript is using it too [4]. So it's also nicer (in my opinion) from a technical perspective. Not just a licensing perspective. [0] - https://github.com/Raynos/mercury [1] - http://elm-lang.org/blog/Blazing-Fast-Html.elm [2] - https://github.com/ghcjs/g

Very relevant: Unidirectional JavaScript talk from Raynos: https://www.youtube.com/watch?v=RLAjMeR8898 The "framework" used is mercury: https://github.com/Raynos/mercury I use "framework" in quotes because it's really just a collection of libraries that work well together. Here's the todomvc: https://github.com/Raynos/mercury/tree/master/examples/todom... All the state in a mercury app is set up first using lenses (bidirectional/bijective data structure) implemented use: https://github.com/Raynos/observ https://github.com/Raynos/observ-struct https://github.com/nrw/observ-varhash If you have any application with state, these three libraries work extremely well together. Basically all the views are pure functions that receive the current state of the app. You can even do "time-travel": https://github.com/Raynos/mercury/blob/master/time-tra