On Jun 4, 2015, at 19:51, Peter Uhnák <i.uhnak@gmail.com> wrote:

On Fri, Jun 5, 2015 at 12:07 AM, Johan Fabry <jfabry@dcc.uchile.cl> wrote:

Alex, they are not evil, they are powerful. And with great power comes great responsibilities ;-)
And great responsibility is a great risk which you need to mitigate, for example by not using threads. :)

But maybe using Job (see Job class>>example) might be a more manageable replacement for fork.

Yes, it would be nice to have a cleaner abstraction for multithreading in the image, but creating this is not an easy task. There are a lot of use cases for such an abstraction. Parallel programming is hard, that’s just the way it is.

I had a quick look at Job and its examples and it does not really seem to abstract that much. example2 even uses fork :-P

---> Save our in-boxes! http://emailcharter.org <---

Johan Fabry - http://pleiad.cl/~jfabry
PLEIAD lab - Computer Science Department (DCC) - University of Chile