News for hackers. Stuff that matters.
Re:Integrating Elm and Phoenix Channels via Elm-Phoenix-socket by nilkn on Monday June 06, 2016 @06:59PM (#11851180)
Elm is very new in the grand scheme of things and it was considered experimental for quite a while. The recent changes show that its developers are still willing to make big changes. But I do believe it's stabilizing quickly and I wouldn't be surprised to start seeing it used a lot more, though still mostly in smaller hobbyist projects simply because even if it stabilizes it's still so new that you can't expect larger companies to risk anything on it.

Elm is a lot more experimental than Elixir, for instance. Elixir is still built on the classic Erlang BEAM virtual machine. And its syntax is fairly similar to that of Ruby, which is an immensely popular language among web developers. Elm looks like Haskell, though, which very few developers are competent with. It was originally based on FRP, which has long been considered highly speculative and theoretical. But I think by shedding FRP it's growing into a very practical language, and while it has a Haskell-lite syntax, it's considerably easier to use than Haskell.

Re:Integrating Elm and Phoenix Channels via Elm-Phoenix-socket by knewter on Monday June 06, 2016 @07:14PM (#11851262)
FWIW, I don't think Cisco counts as a hobbyist shop: https://github.com/CiscoCloud/mantl-ui-frontend

:D

Re:Integrating Elm and Phoenix Channels via Elm-Phoenix-socket by brianhicks on Monday June 06, 2016 @10:14PM (#11851957)
Cisco is doing some cool things in open source and let us (read: the team at aster.is who wrote that) do it mostly how we see fit.

Somehow, though, convincing them to use a language that almost never has any runtime errors was not a hard sell.