Ah yeah. I'm using python now for the same reason. I don't need more concurrency than a couple of servers with a few web threads and worker threads would give me.

PAAS level deployment and failover is sufficient. (Edit: for my needs at the moment)

If you keep your async tasks in memory in any system they'll disappear when you deploy.

So they weren't really reliant on the things that set erlang apart. So the cost of the small support base in tooling and libraries is more significant.

Speaking only for myself, I really start to miss the concurrency options in Elixir when I start coding in something else. I start trying to mash concurrency into the other language & dreaming of GenServers & receive functions.

Have you look at the actor model inside DAPR?

I miss pattern matching

OP may have also been thinking of this older thread: https://news.ycombinator.com/item?id=23283675