Lol, true, I was speaking more of the common CLISP and Scheme implementations. ^.^
LFE is awesome, I highly recommend everyone to play with it. 
GUI’s is a hard problem, QT is near the de-facto for native interfaces now, and HTML for the web. I would not see why Elixir would have a direct interface regardless, it is design to be used on headless servers.
Also, there is ElixirScript, which is new but works, it lets you write javascript inside elixir as elixir code, which then gets sent as javascript out.
Yep, Elm is a fairly pure ML language, it is not like Haskell or OCaml, it is very limited, no higher typing of any sort, it is designed to be quick safe and fast to make simple HTML javascript programs, and it works well at that.
Bucklescsript is OCaml compiling to javascript, it is utterly fantastic, entirely safe and powerful, but it is a newer layer so is still getting libraries on it. My own Bucklescript-tea library adds a near identical to elm interface for writing web programs if you like that style like I do.
You can ‘do’ about anything in any language, but this is the awesome part of Elixir/Erlang/LFE/etc.., they run on the EVM/BEAM, which is unmatched by anything else.
You would not even necessarily ‘need’ to use Elixir either (other than it has a host of awesome libraries that are easier to use in it, but not necessary to use in it), any EVM/BEAM language would work.
The both already are. Any language that compiles straight to the EVM/BEAM must be because the EVM/BEAM must be.
Not much really, the Process Dictionary is probably the most un-functional-like thing but no one really uses that anyway…
