You have a point. I probably did not do a great job of explaining why I did that sort of choice. In retrospect I would have written the article in a different way.

Often your thoughts on a subject don’t become entirely clear until after you have written something, and seen the feedback.

What I wanted to do was to address the idea that Go is somehow incapable of being used to build large systems. In my mind that does not require comparison with the latest and greatest Java. You only need to compare with the Java that has already been used to build large successful enterprise applications.

I don’t know what the Java community is like but I suspect that most really large Java projects today are not using the latest style of Java programming as the project got started in an earlier age.

At least that is what you see e.g. in large C++ projects. They look nothing like modern C++.

I realize that as a Java developer, your perspective is: Is this Go language of any value to me?

To you, it then has to be compared to the latest because that is what is of value to you. I think you might have been looking for a more hands on comparison. Like what can you gain by going for Go today.

But my approach may be seen more like a philosophical take on the difference between Java and Go. How do each language approach development?