1–4 of 4 posts
- Erlang/Elixir
- F#
- Scala
- Clojure
- Haskell
- Elm
Are there others you'd like to mention?
I don't expect a singular "best" list, more a "best for". The context would be for a general distributed tech stack.
* "practical" means actual use regardless of functional capacity.
If you already have investments in one ecosystem or the other (whether in employee skills or in existing, possibly "legacy" applications), that should narrow a choice fairly easily. Similarly if you might expect investments into an ecosystem could give you market leverage (things like "we want our code to be usable/scriptable/API-able by other companies that only know C#/Java/JS").
A big "best for" criteria difference across your list is the question of broader code ecosystem: F# works well with other CLR code (such as existing C# libraries and applications); Clojure works well with other JVM code (such as existing Java libraries and applications); Elm works well with other JS/ES code. If you already have investments in one ecosystem or the other (whether in employee skills or in existing, poss…
For all the rest, that ethos/use-case is a bolt-on set of libraries or frameworks.