The point I'm trying to make is that you can develop and debug Go code perfectly fine without a debugger, as shown by the large-scale deployments of software written in Go. Not adding Go to your tech stack because of that is... not very well thought through, to say the least.
No, it's a very valid concern. It's quite plausible that the absence of a debugger slows down the roll out to production.
Having a debugger is not the only way to debug. Thinking otherwise is not thinking.
I never said it was the only way to debug, just that between a language that only supports `printf` and one that supports `printf` and a debugger, the latter is obviously a more productive environment to work in.