3 ms·

I haven't used Elm, but generally I think it shouldn't be that scary to use an "advanced language" if it has an even remotely decent FFI. It might seem like ho

by mbrock 10y ago

I haven't used Elm, but generally I think it shouldn't be that scary to use an "advanced language" if it has an even remotely decent FFI. It might seem like horror to have to interface to external dependencies, but if the libraries you want to access aren't extremely complex then interfacing with them probably isn't going to be such a huge problem. In some cases you might want to use the advanced language for some things but keep the outer layer of the app in JavaScript. At a previous workplace we had a particularly tricky parsing module written in Fay (Haskell subset compiling to JS).

bbaumgar 10y ago
The latter case has worked out great for us at helme.io. Our computational forecast library is written in Clojurescipt, while the rest of the application is in JS + Angular. A word of warning: with Clojurescript, at least, there is a big cost to converting between JS and CLJS types. This has been a big painpoint as our need for frequent calculations increases. Still, we wouldn't have it any other way.