It may be easier - as you can code it in a more procedural fashion, but you can do it in either system - there are many techniques you can use.
There are also “green threads” libraries (crates) available for Rust. These may over more control over the internal scheduler as well. > On Nov 13, 2019, at 8:02 AM, Serge Hulne <serge.hu...@gmail.com> wrote: > > Am I therefore correct in assuming that, if the problem I am trying to model > is not IO bound or CPU bound, but deals essentially with modeling a large > number of independent cells (a sort of massively parallel « Game of life »), > where each cells lives in its own process, it makes more sense to model it in > Golang rather than rust? > > -- > You received this message because you are subscribed to the Google Groups > "golang-nuts" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to golang-nuts+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/golang-nuts/87f2cdd8-1968-445d-b2bc-eae349ae5687%40googlegroups.com. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/AC558F7E-712B-4F26-B402-00F98514511A%40ix.netcom.com.
