I know I sound like a party pooper, but I thought/hoped that packages in Elm was about providing one really good lib/package for a particular concern (at least as a general rule). Maybe you could help each other out and make the "awesomest ever" phoenix package for Elm.
A quick peak on reddit and I find this too: https://www.reddit.com/r/elm/comments/4kkjly/elmphoenixsocket_a_pure_elm_implementation_of_the/ I think it's super that folks are enthusiastic about providing Phoenix integration support in Elm. So if people still go ahead and do their own thing (which of course they are entitled too), it would be great as a end-user/consumer to get a rationale about why their package was created and how it differs/improves on what's already there. cheers -magnus On Monday, 23 May 2016 11:05:26 UTC+2, Simon wrote: > > Actually no, and it looks like Noah has put more effort into the helpers, > and faced the same complexity in actually extracting messages incoming > On 23 May 2016 12:14 a.m., "Magnus Rundberget" <[email protected] > <javascript:>> wrote: > >> Did you notice this before you set out on your quest ? >> http://package.elm-lang.org/packages/NoRedInk/elm-phoenix/1.0.0/ >> >> Cheers >> -magnus >> >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "Elm Discuss" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/elm-discuss/n06mRcIiesI/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> [email protected] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
