Modelling a problem like this with tons of Erlang processes tends not to go very well: - It's slow, really slow, and memory heavy. All communication between pr

Modelling a problem like this with tons of Erlang processes tends not to go very well: - It's slow, really slow, and memory heavy. All communication between processes involves copying and context switch. - It's easy to introduce deadlocks (A calls B calls C calls A - now system is stuck) or unbounded message queue growth (if you use casts rather than calls) - Everything is a single unit of fault tolerance (if one cell crashes, the entire simulation should be re-initialized from a known state) so all the processes need to be linked together in a massive web, which more or less defeats the point of process isolation. I think it might make sense in the abstract actor model, it just doesn't map cleanly to Erlang processes.