Spring and Java aren't junk. I like Go for some things, but when using it I miss many things from Java: * I can connect to the running JVM and change log leve

Spring and Java aren't junk. I like Go for some things, but when using it I miss many things from Java: * I can connect to the running JVM and change log levels, and other parameters live. * I can debug a Java file that has compilation errors in it and fix them as I go in some cases. (In Go you can't even compile a file with an unused import) * Java libraries and frameworks are mature. Some have been around for decades with all the testing and refinement that implies. For some applications, like a REST server connecting to a database, why would I use Go and use all it's brand new, limited libraries when I could use dropwizard instead and get an easy to deploy JAR file? Sure Java has some esoteric features, but you don't have to use them. If you can't keep your team from being clever in Java, I doubt you'll be able to do so just because they use Go. I've seen many Go libraries attempt to use introspection and backtick 'annotations' to very confusing and buggy effect.