[ninjakeyboard]

"I think there's a sweet spot for a language that accepts mutability inside of actors, but only allows immutable objects to be sent as messages, with an escape hatch available if needed."

That's kind of what akka is on scala or java. Messages are immutable _BY CONVENTION_ but you can do whatever you want.

[overkalix]

Isn't that the basis/point of the actor model? Actors can message each other and processing the message can trigger state mutation of the recipient, but they can't directly mutate each other.

[lpil]

All data is immutable on the BEAM with a few exceptions, so no mutation within actors.

[dnautics]

No, that's not true. Actors in elixir/erlang mutate their state through tail call recursion through the loop function.

[lpil]

I said data is immutable on the BEAM, actors can update their state.