Beto I was correct people's homework assignment in Java over 20 years ago, so I am not new to Java.

That a language is easy to learn and simple is an important attribute when you try to create large systems as you will typically tend to hire a large number of junior developers which you need to train. A complex language with a lot of mistakes which are easy to make such as C++ will quickly lead to poor to maintain code with hard to track down bugs and slow development.

Java does indeed seem to replicate many of the worst problems of C++ such as growing too complex.

If you think Go is some sort of quick script coding language to replace JavaScript then you certainly know Go far less well than I know Java. Go has been designed for large scale development. Java was not actually designed for large scale development. It is just being used for it.

That is how the industry works. JavaScript was never designed for the scale it is currently used. Yet the industry often go down unexpected pathways.

I had hoped to show that Java code can easily produce less reliable code than Go in this article. But I seemed to have failed to convey this point.

This is an intersting topic to discuss. And frankly all I want is for Java developers to demonstrate to me with some examples why they think Java is better suited for large scale development or what exactly convinve them that Go is not up for the job.

I have yet to see any convinving arguments. Only arguments that points to more or less complete lack of knowledge of how Go works. One told me Go does not have execeptions and is thus bad. It does, so that it wrong. Another insisted Go only treats errors as error codes. It doesn't. It uses error objects.

Yet, people feel a strong desire to take a dump on my Java skills or knowledge. Look yourself in the mirror folks!