I completely agree that we shouldn't use Native modules for things that can be written in pure Elm. If I want runtime errors I will use Javascript, thanks :D
If my understanding is correct browser apis are not possible to write in pure Elm, for example http or web storage for that matter. I think once those things are covered we won't need to use JS anymore. But until then if you restrict usage of Native modules to browser apis and make it official we could create "web platform" faster with more contributors. Any libraries that use native code as wrappers for existing Javascript libraries should be rejected. On Thu, Jun 2, 2016 at 9:35 AM Evan <[email protected]> wrote: > Use ports! > > Support for "web platform" things will expand as quickly is as manageable > with all the other things that need to happen. > > > On Wednesday, June 1, 2016 at 3:45:48 PM UTC-7, Frederick Yankowski wrote: >> >> I have not seen any such documentation. One has to work from examples. >> And the Elm leaders (broadly speaking) actively discourage us from writing >> native code and effect managers. >> >> On Wednesday, June 1, 2016 at 5:14:30 PM UTC-5, Leonti Bielski wrote: >>> >>> Hi Frederick! This is awesome, thanks! >>> Is there any documentation on how to write native modules? >>> >> -- > 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/oQz5_HvsdcQ/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > 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.
