Yes, but isn't there an important class of concurrent software where lightweight threads work on shared state? Isn't that the reason for "goroutines" in Go, and STM in Clojure, and actors in Scala?
Stephan Eggermont-3 wrote > On 23-10-17 15:27, horrido wrote: >> Do I just say that if you need concurrency, Pharo is the wrong choice? >> After >> all, no programming language can be good at everything. You must always >> choose the right tool for the job. > > No, you tell them to use many images and/or vms. We can effectively use > state-full micro services. Immutable data is still rather inefficient > and in many cases we can avoid needing that. > > Stephan -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
