I've spend some time with Go, but never felt overly productive with it. As someone else in this discussion mentioned a simple language doesn't mean that solutio

I've spend some time with Go, but never felt overly productive with it. As someone else in this discussion mentioned a simple language doesn't mean that solutions in this language are simple! Look at what real problems you have to solve in you applications, and then tell me that generics in a statically typed language are not important! Go applications are full of useless code to circumvent this restriction. Want to make something immutable? Not very convenient in Go, very easy in most other (statically typed) languages. While Scala has a complex type system it is a simple language at it's heart. For example try-catch is not a special language feature but another application of the powerful pattern matching. It will take a little longer to learn Scala compared to Java, but you get a much better tool to solve the most problems. And you get all the libraries and the tools (any Go IDE on the level of IntelliJ or NetBeans?) of the big Java ecosystem. But even if you don't want to use Scala, you could be more productive with Java than with Go. From a Java perspective Go has not much to offer, not even fancy concurrency.