> Channels will be a better fit inside .NET? I suppose? > Without true experience with any of agents/channels, what make it simpler? If you are very clear ab

> Channels will be a better fit inside .NET? I suppose? > Without true experience with any of agents/channels, what make it simpler? If you are very clear about not retaining references to things you ship to another actor, Erlang is marvelously concurrent without any of the usual considerations for shared memory or functional programming we have to make. You can confidently manipulate and mutate variables in your actor scope because your actor is single threaded and OTP makes async-with-response calls trivial to mix in with this when you want function semantics. Actor based systems give you a place to put sequential mutation code and a clear, clean, scalable way to define parallel operations. Channels really... well they give you this blunt force instrument to export data but you end up implementing actor-like management every time they're invoked if you're doing any sort of fan-out anyways.