Re:Integrating Elm and Phoenix Channels via Elm-Phoenix-socket
by inopinatus on Monday June 06, 2016 @11:03PM
(#11852102)
Yeah, I had mentally tagged Elm as "interesting language that future browser languages/frameworks might claim as an inspiration".
But, I thought the same about Coffeescript. And then Rails gave it massive traction. I wonder if the same might happen to Elm, should Phoenix adopt it as their browser language of choice. That might also offset concerns about Elm's fledgling status and key man risk.
Re:Integrating Elm and Phoenix Channels via Elm-Phoenix-socket
by qohen on Tuesday June 07, 2016 @01:58AM
(#11852672)
I wonder if the same might happen to Elm, should Phoenix adopt it as their browser language of choice.
There's definitely a connection there -- for what it's worth, the keynote at 2016's Erlang Factory conference was a shared talk between Chris McCord (creator of Phoenix) and Evan Czaplicki (creator of Elm), "Making the Web Functional" [0]
Re:Integrating Elm and Phoenix Channels via Elm-Phoenix-socket
by tel on Tuesday June 07, 2016 @08:12AM
(#11853874)
Having used them both quite a bit I really cannot say that Redux is much at all like the Elm Architecture. It separates views and state machines. This works well for managing state in an application-wide sense but complicates state which is more local to your components.
As far as why people don't just use Elm, I think it's the same reason functional language are less popular in general: fewer familiar engineers and steep learning curve.