Adam Warski - Concurrency in Scala and on the JVM

Concurrent programming is one of the areas where Scala shines. Due to its flexibility in defining new abstractions, we can enjoy concurrency toolkits that provide declarative concurrency APIs. They often eliminate the causes of race conditions or deadlocks at their source.
Despite concurrency being Scala’s specialization, or probably because of that fact, the landscape of concurrency libraries and frameworks is dynamic. There are a couple of approaches that have been gaining popularity: starting with Akka, through Monix, cats-effect, ZIO, joined recently by a new contender: libraries based on JVM’s Loom project.
Let’s characterize the various approaches to concurrency, revealing their strong and weak sides so that you can pick whatever suits your project best. We’ll consider safety, developer experience, readability, interaction with effect systems, type-level guarantees, and more!

Great overview! I personally prefer the functional approach despite the syntactic overhead.

[@programmer-z9b]

You don’t use onComplete when dealing with Future in actors of Pekko/Akka,but you use pipeToSelf code block in which you define commands to be sent in both Success and Failure case, to the actor’s next behavior it will transition to.

[@avalagum7957]

No Cats were mentioned here? By the way, I always like all Adam's talks, live coding and blog posts.

[@albertbosshard9942]

Actually, cats-effect was briefly mentioned at the beginning (around 2:31).