3 ms·

I don't really think that too many people are aware of Hewitt et al's intentions behind the Actor model - e.g. no global knowledge (emulating a scientific commu

I don't really think that too many people are aware of Hewitt et al's intentions behind the Actor model - e.g. no global knowledge (emulating a scientific community), actors can only send messages to known acquaintances, only async messages, no need for additional baggage per actor such as mailboxes or lightweight threads. I'm not sure that matters here though. The author is clearly interested in developing a derivative of Erlang/OTP that works for the author. Erlang is often described as an implementation of the actor model.

dbeck74 10y ago
I respect the Erlang/OTP model a lot. This library is inspired by that. I don't have the illusion to get anywhere close to it in a reasonable amount of time. There are also differences to the Erlang/OTP too. This library uses typed messages and taking advantage of the compiler to do type checking. I found it is easier to create this library if 1) the number of input and output channels are fixed 2) the topology of who sends to whom is fixed when the tasks are passed to the scheduler.