purescript-signal

I agree, this is one of Elm's main draws. PureScript has a library for this style of FRP (https://github.com/bodil/purescript-signal). From the documentation, Elm signals are like a process network (https://en.wikipedia.org/wiki/Kahn_process_networks). In my experience I've been able to model any conceivable interactions with a website using this model.

There's also PureScript, which is a little more "apples to apples" with Haskell. Both the Elm and PureScript compilers are written in Haskell. http://www.purescript.org/ https://leanpub.com/purescript/read Also, some of the ideas from Elm are having an influence in the PureScript ecosystem. For example: https://github.com/bodil/purescript-signal See also: https://github.com/slamdata/purescript-halogen

I won't argue that Elm does anything other than an exemplary job at #3, but it is worth noting that there are some interesting efforts to build similar functionality in PureScript libraries: https://github.com/paf31/purescript-thermite https://github.com/kRITZCREEK/reactive-psc https://github.com/bodil/purescript-signal https://github.com/michaelficarra/purescript-demo-mario https://github.com/mechairoi/purescript-frp-rabbit To me, this is the benefit of PureScript - yes, you have to do a little more work, because you don't get these things for free from the compiler and tools, but you gain complete control over your application structure. You're not forced to work in some ambient Signal category.