Being able to utilize erlang libraries means there are a ton of heavily production tested libraries you can easily drop into an elixir project.
I also encountered some pain with the AWS client for Elixir when our company implemented SSO. There was a lack of support for a certain flavor of environment variable if I recall correctly. It's not horrible, just a pain.
hard disagree on all but c++, .net and maybe python
I think people forget erlang has been around a long long time and I've written ruby for years and can speak with great confidence that the equivalent ruby libraries in elixir are typically much higher quality
The single unix process that BEAM uses is more conducive to some kinds of systems than some of the hackier-feeling solutions for the Rails ecosystem to tie different pieces together.
What's the issue with Kafka and Elixir?
Things I like using it for:
- long running services
- doing anything w/ concurrency
- setting up cron-like processes that run every so often
- actor model anything
- stateful services
- web development using Phoenix & Ecto
- parsing
- encoding/decoding
Things I don't like are primarily related to it being a small enough community. That means libraries for third party services aren't always the best, and using it in the enterprise means that the smaller talent pool is less attractive when the company's priority is to use proven/boring tech for which you can hire tons of developers. I also don't think Elixir has a clear value proposition when you're writing small, single purpose functions for a serverless architecture (even though I really like writing it), or when you're company decides to go all in on Kafka for communication between micro services.
Just my two cents.