[destevil]

for large systems, you really can't beat the implicit infra that Java and .NET bring to the table. I am dealing with 20 year old VB code that interops with new .NET core code just fine. Try saying the same for Python.

The larger issue with Go, which Go enthusiasts will downvote me for, is that it allows for writing absolutely garbage code that is impossible to read. Readibility is king in software development, and developers spend 80% time reading it. I won't go into the details here, but Go has no constraints for how code should be structured, leading to spaghetti code. I have first hand experience, and 30 years professional experience.

[capl]

Good point regarding .NET! The .NET CLR / VM is clever in that way.

Regarding your experience with readability in Go, I have to agree in some way because the known (and controversial) explicit error handling, but what you may realize sooner or later is that handling both the happy path and erroneous path is actually a net positive. That's the difference between seeing `if err != nil {` as code pollution or actual logic. I've realized the latter.

[destevil]

This older reply is pretty exhaustive. Go leaves critical readability structuring to devs (a bad idea).

https://news.ycombinator.com/item?id=38128698