Hi everybody,

Sadly I don’t have the time to participate on all the so interesting discussion 
about concurrency and actor stuff.

But I have a question. 

I am working for 6 months in the Scala/Akka world, on a project (server stuff 
in a docker kubernates world) and after six months of work, and talk with Scala 
experts we are abandoning the actor paradigm. It is true that quickly the code 
is hard to follow, maybe our fault but I have to say that it seems me that the 
nature itself of the actor system bring some opaque way to follow what happen 
in the system. Even for a small set of actors.

It has been very fun to try an architecture based on Actors, but at the end, 
this is not easy to see what use case they are good for.

Then I wonder if we/you have good use case where Actor paradigm can show real 
advantages ?

Something obvious to me that the dev tools would need to be very advanced for 
debugging in case of actor model use.

Cheers

Gerard
_______________________________________________
swift-evolution mailing list
swift-evolution@swift.org
https://lists.swift.org/mailman/listinfo/swift-evolution

Reply via email to