Almost regularly I see Scala code where people program in a sequential, synchronous style and integrate an asynchronous I/O call by waiting for its completion with Await.result. But you really shouldn’t. Let me start with a quote from Viktor Klang, the author of the Scala Futures library: Some find it bad that Await.result is *outside* of Future. I find it bad that I added Await at all. #retrospective — Lgd. Viktor Klang (@viktorklang) November 9, 2015 Why is Await.result bad? If you call...
