Go, because

• I can decent crank code out quickly, and good code when I need to.
• The tooling is outstanding
• I can easily jump back into my projects I haven't touched in a year and do bug fixes. Which most of those is project organization (and some of my projects are less well organized and harder to get back into), the language facilitates it by being simple. The hardest problems I face are algorithmic, not fighting with the compiler
• Astonishingly fast compile times. I really hate waiting for builds, and CI pipelines run so fast
• Static binaries. Before Go, I spent several years in Ruby, and got sick of having services fail because of runtime dependency changes. I had interpreter updates itself break programs more than once.

I was using Java in my job, and had been since 1995 at that point, and did not touch it except for work. When I finally got fed up with dynamic, interpreted languages (around 2008?) I evaluated Rust, Vala, and Go, and Go won. In retrospect, I'm really glad I didn't pick Vala, but whenever I look into Rust these days I'm also glad I didn't pick that.

For scripting, now I stick to bash, or zsh if I'm not sharing the code. Bash scripts never fail because bash changes; the biggest risk is having to be careful with commands; tools I've become accustomed to, like ripgrep, aren't guaranteed to be installed everywhere, and POSIX tools like grep have variants that differ in argument support: GNU grep is substantially different from SysV grep. If I'm distributing it and can't write it using basic, standard bash and the standard SysV POSIX tools available in BusyBox, I write it in Go.

I did do a project in V recently and like it a lot, but it's not mature enough to switch to, yet, and it's so close to Go I can't switch between the two because I start to conflate them.

I will very rarely program in C to fix a bug in some project I'm using. C is so basic, I'll never forget it; the biggest hazard in C is other people's idioms.