Integrating Elm and Phoenix Channels via Elm-Phoenix-socket

Re:Integrating Elm and Phoenix Channels via Elm-Phoenix-socket by oomkiller on Monday June 06, 2016 @07:35PM (#11851372)

That last part sounds pretty cool, how is this sort of thing being encouraged?

[ Parent | on HN ]

Re:Integrating Elm and Phoenix Channels via Elm-Phoenix-socket by knewter on Monday June 06, 2016 @07:51PM (#11851434)

As a corollary to what shados was saying, now that 0.17 is out the elm-lang organization will make a library to cover every single part of the web platform [0], at which point you will never need to.

[0] https://platform.html5.org/

[ Parent | on HN ]

Re:Integrating Elm and Phoenix Channels via Elm-Phoenix-socket by shados on Monday June 06, 2016 @07:47PM (#11851418)

I'm no Elm expert, but as far as I understand, the "native library" APIs, the kind that are used to actually wrap browser APIs and interface with javascript in a way that can be published and made reusable, is "private". I mean, you can look at the source and make your own, but you're playing in undocumented, unstable territory.

The only "official" interop channel is the "port" system, which only lets you do a publisher/subscriber type thing with your application at runtime, and cannot be used in a library.

So you basically cannot make a "blessed" library that uses native browser APIs.

[ Parent | on HN ]