5 ms·
It was also rejected at my workplace, with the extra reasons: 4. The language is still unstable. Porting our code to the next release could be a huge task. 5.
by idoubtit 7y ago
It was also rejected at my workplace, with the extra reasons:
4. The language is still unstable. Porting our code to the next release could be a huge task.
5. Elm + JavaScript is generally painful.
6. Few libraries, some of them unmaintained. Combined with the near-impossibility to use JS libraries from Elm, it would increase our work too much.
- vmchale 7y agoI did a side project in it; then the dependencies broke because of a compiler update (frustrating), and that's never been updated. I would never use such a thing in production.
- Karupan 7y ago> Elm + JavaScript is generally painful Getting rid of kernel modules for everything others than core packages in 0.19 made JS <-> Elm interop even more painful and broke some apps. I forked the compiler [1] to support that, although it is not upto date (still stuck at 0.19.0) [1] https://github.com/Checksum/elm-compiler https://github.com/Checksum/elm-compiler
- razze 7y ago6. Name one language, that has no unmaintained libraries, please :)