Scala vs Go
<i>&gt; Scala code can be very dense and hard to grok at the early stages of learning.</i><p>This seems to be the crux of his argument, and I think it&#x27;s a rather poor one.  I have used both Go &amp; Scala professionally.  Yes, it took less time for me to start writing real code in Go.  However, I found Go&#x27;s &quot;simplicity&quot; to be limiting and frustrating when it came to building production applications.  Things like the weird split between functions returning errors but occasionally panicking, lack of inheritance, and poor dependency management through github links make Go a poor choice for applications within a business setting.  Scala does allow for more variance in individual coding styles, but not so much that an experienced Scala programmer can&#x27;t read &amp; understand other peoples&#x27; code with relative ease.  It&#x27;s a non-issue during development as long as the team agrees to follow the same set of conventions, just like any other language.