[aldousd666]

I worked with a team that was convinced of the superiority of elixir/erlang over ruby/rails in our ecosystem. It can accept thousands of simultaneous connections, etc. But the devil is in the details. If those connections include queries to a database then it's just a slow and clunky as every other front end framework and the learning curve is pretty damn steep. So overall the lack of integration with existing tooling and communities is what drove us away. Sure, you can do magnificent things if you keep every little bit in process but it's really hard to do that. And you need a super big box to make sure that everything is in one process.

[ipnon]

Elixir is like a magic potion for network-bound applications, but most people aren't working on network-bound problems. It still has the elegance and consistency when you're writing a regular application. You just have to know the basics of functional programming to grok the program flow.

[atonse]

The combination of elixir and postgres served us well for years. I describe it as an extremely boring stack (in the most loving of ways) – no drama.

But it's just like any other framework in that, if you want to write bad code, it won't stop you.