[smallstepforman]

Dang it, we lost 2 of the biggest champions of the Actor model, Carl and Joe a couple of years ago. Who is left to carry the torch to illuminate millions of developers who have no idea or have never heard of the Actor model? Sadly, we will see thousands or poorly thought out replacement models (eg. C++ futures, thread pools etc), which only offer a subset of Actor functionality instead of implementing the whole she-bang. E

[dangets]

I wouldn't say that the actor model is going away. There are several new-ish projects built around it or retrofitting it in more common languages.

- Elixir (and Erlang) https://elixir-lang.org/

- Akka - JVM and .NET frameworks - https://akka.io/ https://getakka.net/

- Actix - Rust framework - https://actix.rs/docs/actix/getting-started

- MS Orleans - https://learn.microsoft.com/en-us/dotnet/orleans/overview

- Pony - https://www.ponylang.io/

[justin66]

> Who is left to carry the torch to illuminate millions of developers who have no idea or have never heard of the Actor model?

Douglas Crockford.

https://www.youtube.com/watch?v=R2idkNdKqpQ

[KerrAvon]

All Mac and iOS developers will eventually be exposed to it. Swift's concurrency support is based on the actor model and has a construct named "actor," which does what it says on the tin.

[acje]

Wasmcloud community? https://wasmcloud.dev/