I don't know pi calculus well, but I don't think Akka has ever really thought in those terms. Frankly, Akka is currently lower-level than that. For example, does pi calculus cope with unreliable channels? The reality of unreliability is front and center in Akka, and that strongly affects how you think about it.
This subject comes up now and then on the Akka list -- folks want to be modeling high-level process flow, and find that Akka is a bit too close to the metal for what they want. (This usually starts off with someone complaining about the fact that Actors don't compose.)
My general sense (and I get the impression that others feel the same) is that Akka is a toolkit that you could build that sort of higher-level view *in*, but it isn't that itself. At least, not yet: they basically started down at the low levels of the stack, and it's gradually evolving up the semantic layers. (Eg, there *is* a dataflow-expression DSL in Akka, but I don't think it's getting tons of usage yet.)
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
(no subject)
Date: 2014-03-21 04:38 pm (UTC)This subject comes up now and then on the Akka list -- folks want to be modeling high-level process flow, and find that Akka is a bit too close to the metal for what they want. (This usually starts off with someone complaining about the fact that Actors don't compose.)
My general sense (and I get the impression that others feel the same) is that Akka is a toolkit that you could build that sort of higher-level view *in*, but it isn't that itself. At least, not yet: they basically started down at the low levels of the stack, and it's gradually evolving up the semantic layers. (Eg, there *is* a dataflow-expression DSL in Akka, but I don't think it's getting tons of usage yet.)