[tomohawk]

After a long stint in enterprise Java land, Go was a really big adjustment. Mostly about letting go of unnecessary complexity. I didn't realize how much I didn't miss that complexity until I recently went back into Java. If you learn the golang way of doing things, the issues this guy mentions really are not something you run into.

[jstewartmobile]

One of the commenters on lobste.rs called boilerplate-heavy Go written by programmers coming from Java "Gova".

From a lot of what I've seen, that is a useful description.

[didibus]

I think Go will suffer the same fate as Java. Any enterprise language that becomes too popular will slowly devolve into an enterprise monster.

If you come to Java with a blank slate, and try using it with simplicity in mind. There's not much wrong with it. But once people add design patterns, layers of layers, reflection, annotations. Etc. You get a monster. And somehow, the enterprise world seems to always create those.

[astrange]

The problem with Java is that there isn't enough of it to have anything wrong with it. The programs have all those design patterns because the language lacks so much power that you have to write it all yourself. For instance, having value types would really help.

The one thing they should take away is namespaces. You can't write unreadable enterprise software if you can't put every 10-line class six packages deep for no reason.

[masklinn]

> One of the commenters on lobste.rs called boilerplate-heavy Go written by programmers coming from Java "Gova".

Not exactly a novel take: https://dirtsimple.org/2004/12/python-is-not-java.html