[jbothma]

Could you find the link? I'm not sure kubernetes can really replace erlang. Some of the key things that distinguishes erlang are

- light "threads" and supervision of them

- OTP which is largely a library other languages with message passing and light threads could implement

- garbage collection per light "thread" rather than stop-the-world

Akka was on the right track in supporting the same approach to highly concurrent and fault tolerant software. The JVM might have gotten better at garbage collection without paid plugins since 2015 when I last used Erlang?

But I'm curious what stack in particular is seen as superceding erlang.

[rapsey]

It does not have that much content in this regard really.

https://news.ycombinator.com/item?id=27192873

[jbothma]

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.

[devoutsalsa]

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.

[mycall]

Have you look at the actor model inside DAPR?

[jbothma]

I miss pattern matching

[blackshaw]

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

[AtNightWeCode]

Akka, Erlang, Service Fabric and so on are based on the Actor Model. You can implement that pattern in any modern language I would say. It is good when it comes to concurrency handling and it can be very simple to understand and to use but async programming is the modern way to solve many of those problems.