(full disclosure: I'm seasoned with Go and haven't used Scala past playing with it in a REPL) I would argue that Go is far more readable, and simpler to grok,

(full disclosure: I'm seasoned with Go and haven't used Scala past playing with it in a REPL) I would argue that Go is far more readable, and simpler to grok, than Scala, and that's without adding Akka on top of it. That's with respect to the level of this project - how much it does, and what it's doing. If you have a huge, distributed system project, I'm sure there's a lot of things Scala would make easier over Go's rabid simplicity. You're also ignoring the points he made WRT portability and dependencies. Scala/Akka still need the JVM, and potentially a bunch of other dependencies. When all you have is a ..., everything looks like a ..., and what not.