I'd recommend making the proposal with concrete use cases in elm-dev to be discussed, but then move on and use ports and get the job done with JavaScript.
Native is mostly undocumented and apparently discouraged. Elm is (very) good for what it has been designed, but it's design process starts from specific use cases and it takes time. --- Personally I'd like to see some kind of promise/task port, since most of the times I send to JS I want to listen for a result/error coupled to that submission (like making a jsonp call), and promises/tasks ports would make that kind of interop feel a lot more natural in Elm. -- 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.
