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.

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

> 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

6. Name one language, that has no unmaintained libraries, please :)

> 2. Fixing some important compiler/library bugs takes years > > 3. No way to host private package repositories

That's kind of related to the dictatorial community management. Relatedly, you still can't write a generic sort function.

You can either write a comparison function that returns an Order, or a function that converts your type to a comparable. Then you use List.sortBy or List.sortWith. I don't really know how a generic sort function would work without typeclasses/interfaces.

For 3., we use elm-git-install https://github.com/Skinney/elm-git-install