On Mon, Mar 13, 2017 at 11:06 AM, Oliver Searle-Barnes <[email protected]>
wrote:

> What do you think, does this offer a practical route to a greater number
> of pure Elm integration libraries?
>

I seriously doubt it.

The practical route is actually joining forces. It is using multiple pairs
of eyes and multiple brains to solve the Native problem as a community.

Some JS libraries are well designed and their code could be used reasonably
safe within an Elm environment.
You'll still have to assimilate them, that is to adapt their API usage to
the Elm way of managing effects.
This would require a reasonable amount of thought but it can be done and
should be way easier than just reimplementing the functionality in pure
Elm.

In some case, a full reimplementation with Elm paradigms using only bits of
JS code from some source inspiration library might be in order.

In some other cases, the quality of the library is so damn poor and the
assimilation effort is so large that it might make more sense to just write
it from scratch.

The way forward, as I see it, is the generation of a proper documentation
for Native. Not only in the sense of "this is how you do it" but in the
sense of a solid checklist that would make sure you are doing the best that
you can to provide as much reliability as it's possible given the context.

What we have now is the  *AbstinenceONLY™* gospel.
We need proper sex-ed. :)

Just to be explicit, I'm not expecting this from Elm's core team. This
should be a product of the community.
In the absence of this semi-official approach, people will hit unmet needs
like the above mentioned firebase integration and the will try to fulfill
them using Native, potentially breaking a lot of the good practices for
Native code.



-- 
There is NO FATE, we are the creators.
blog: http://damoc.ro/

-- 
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.

Reply via email to