News for hackers. Stuff that matters.
Re:Elm from a Business Perspective by b123400 on Thursday November 10, 2016 @09:32AM (#12920615)
You definitely have access to something we don't, and that might changes how you view Elm. For example a normal Elm user can only send/receive values to/from JS via ports, and that is not scalable, e.g. you are not suppose to use ports in library. But at NoRedInk I guess you have some sort of native module wrapper (https://github.com/NoRedInk/take-home/wiki/Writing-your-firs...) that we cannot access?
Re:Elm from a Business Perspective by elbear on Thursday November 10, 2016 @10:17AM (#12921027)
Anyone can write a native module. You can't publish it, but you can use it in your project.[1]

[1] http://faq.elm-community.org/#why-doesnt-the-elm-compiler-fi...

Re:Elm from a Business Perspective by lgas on Thursday November 10, 2016 @10:57AM (#12921456)
Native modules are accessible to anyone. Unfortunately the link you provided is a little out of date despite being the top hit on google. Here is an example of a native module that works with 0.17 though: https://github.com/evancz/elm-markdown/blob/master/src/Nativ...
Re:Elm from a Business Perspective by b123400 on Wednesday November 16, 2016 @09:50AM (#12967288)
Yeah I figured the "rules" to write a native module for a while, but there is no tutorial, no support at all, which makes me rather uncomfortable, and I am never confident with that code.