They solve different problems . Actors are good at solving task parallel problems . While parallel collections are good at solving data parallel problems .
I don't think they are mutually exclusive - you can use parallel collections in actors and parallel collections containing actors.
Actors library in Scala is just one of the options, approaches to concurrency, among many (threads & locks, STM, futures/promises), and it's not supposed to be used for all kinds of problems, or to be combinable with everything (though actors and STM could make a good deal together). In some cases, setting up a group of actors (workers + a supervisor) or explicitly splitting up a task into portions, to feed them to the fork-join pool, is too cumbersome, and it's just way handier to call . Par on an existing collection you're already using, and simply traverse it in a parallel, gaining a performance benefit almost for free (in terms of setup).
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.