The generalization of anecdotal experience is a flaw in any argumentation. We see it every day everywhere. You *assume* that Go creates sooner or later problem

The generalization of anecdotal experience is a flaw in any argumentation. We see it every day everywhere. You *assume* that Go creates sooner or later problems everywhere it runs. I have another anecdotal data point: At my workplace the most troublesome services are the ones written in Java. The Go services are much easier to manage and run much more reliably. Actually I can't remember of any issues with Go services. So, you need to take more data points into account to come to a justified verdict. Your generalization of Go leading systematically to huge problems is far away from reality. There's already a huge amount of services written in Go. Networking stuff, backend APIs, CLIs, databases, ... do they all fall apart? No, just the opposite: They are some of the most successful projects in the last years. Your analysis of the (tiny) problems is correct. Your conclusion that people shouldn't use Go is very wrong.