2 ms·
Yep every 'native' library needed arduous review process via github issues. I waited for over a month for elm overlords to approve my 'native use' library , the
by dominotw 11y ago
Yep every 'native' library needed arduous review process via github issues. I waited for over a month for elm overlords to approve my 'native use' library , they simply closed the issue.
Dropped elm for react and co. Now I have serverside rendering, code splitting, working debugger ect which was impossible with elm.
This was last year though so not sure if it is still the process. YMV.
- jmite 11y agoIt has changed, in that the language is moving away from Native code, and instead is trying to provide the web-platform as part of the language/core libs. And for everything else, there's Ports. You can't use them in libraries, but for your own projects they're a much better JS FFI.
- dominotw 11y ago>And for everything else, there's Ports. Ports are extremely tedious to use if you are doing anything even moderately complicated .