Thanks Sergiy for your suggestions. I am looking at your suggestions and reflecting on how to incorporate them in my article to represent Java in a more fair fashion. I think a big challenge for me is that Java at this point isn't really one language but multiple packaged as one. How do you compare anything to that?

It is like a language that contains Haskell, C and C++ all in one and then I do a comparison with C.

Of course for you it would be easy to triumphantly point out that your language is better than C, because it contains all these other languages including C.

The primary problem is that containing 3 languages in one package produce far more complexity. Simplicity is a feature often not taken serious.

And the latest features added to Java are not really of any interest to this discussion as this is really about how Java has been used. Large systems have been built using Java, without any of the features you mention.

The claim from the Java guys has basically been that you cannot build such large systems with Go. To counter this claim we have to look at what Java features was commonly used to build existing large systems.

But I agree that it is fair to show that modern Java also offers modern high level features to reduce verbosity. I will look at ways to cover that in a more fair fashion than I have.