RE: https://mastodon.social/@zeank/116227033836243730

An excellent article about the limitations of the actor model in concurrent programming and how Erlang is still the best tool for this job.

@janl I have mixed feelings about this article. I agree that full isolation has issues, but I disagree that untyped messages are bad and that Akka is bad because it's embedded in Java. In Akka's case, the value of being embedded in an existing language more than outweighs the drawbacks, imo, and the author shows how relaxing isolation has all sorts of benefits so I would have expected Akka to compare more favorably in the end. The killer feature of shared memory that goes unmentioned is the ability to use immutable persistent data structures that share structure rather than copying (for actors in the same OS process). The deadlock scenario in Erlang is indeed bad, though. If Erlang had promises like JS then A -> B -> A would not deadlock.
@dthompson Interop wasn’t part of this discussion, so I’m not reading this as Akka-bad, just Akka-access-to-any-old-shared-state, while Erlang does narrow and deliberate shared state.