Just had a quick look at Unpoly - and the first thing that struck me was the reliance on CSS, and the fact that it’s all just JS - with the usual JS ‘null is not an object’ type errors on the horizon?
Since using Elm, I have been able to rid myself of the problem of managing CSS altogether - no need for CSS at all. And if it compiles, it runs without error. As a functional language it has a lot in common with Elixir, which I like. The cognitive load of switching from front end to back end is reduced. There are differences, obviously, but I’d rather use Elm/Elixir than JS/Elixir.
Not suggesting you’re wrong, I’ve been more of a hobbyist, using Ruby/Rails/JS and now Elixir/Phoenix/Elm to build apps to help run my company. I’m sure I don’t have the commercial experience you have.
I guess I should be an Elm envangelist I have yet to find a front end problem I can’t solve with Elm.
Oh, and Elm and Phoenix Websockets are a great combination