With today’s powerful multi-core processors, the demand for efficient software concurrency is high. We find strong support for such concurrency in the latest crop of “modern” languages such as Clojure, Elixir, Go, Haskell, and Scala.
Whenever I present Smalltalk (Pharo) as a great language option, inevitably someone asks me about multi-core software concurrency. I have no response for them. 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. Do I say that doing concurrency right is very, very tough, even for the most experienced of developers? Let's focus on Pharo's strengths, instead. Sounds like an excuse. Can we safely ignore the multi-core reality? I welcome your feedback. -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
