Oct. 23, 2017
2:17 p.m.
That's the GemStone model. It works well for our customers. On Oct 23, 2017 07:03, "stephan" <stephan@stack.nl> 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