(new talk, I think could be very exciting actually, we've had numerous tradeoffs made, some bad which we backtracked on, some good which formed the core of Akka until this day... It's mostly about design tradeoffs, but on specific cases that could be interesting to debate with others I think afterwards :-))
In this talk we'll discuss several APIs, and their evolution. From successful design decisions, to dead-ends which had to be removed. Over it's lifetime Akka has seen multiple core APIs that have led vastly different lifes, such as the schedulers, core Actor APIs for creation as well as of course message sending APIs which saw the most evolution but also the more time went by, the more minimal and precise they got. And of course the evolution of the Akka Streams and Reactive Streams API/SPIs, that have seen numerous iterations before seeing a stable API that we were confident would