Between Go and Rust for infra, let's say that Go is the #1, Rust if far far behind. Most recent infra tools are built in Go, Kubernetes, Docker, Prometheus, Grafana, Terraform etc ...
What’s the deployment story like ? Here’s a hot take of mine: we should treat our users as master and make their lives easier, not ours.
That’s a hot mess to manage.
There is one thing I believe Go is by far and away the leader at: keeping codebases maintainable over time.
Go is designed very clearly with this goal and it's excellent at it. The verbosity you complain about makes it much, much clearer what something is doing. That coupled with some of the baked in opinions means it is significantly more straightforward to pick up code that you or someone else wrote a few years ago and modify it.
Yes, your codebase is nice and elegant and maintainable. But you haven't shipped as many features as the Python or Java developer, haven't delivered as much value to customers. Ultimately, the users suffer. It's a form of selfishness.
If I write code more slowly that others find easier to maintain, that is selfish?
https://github.com/Hello-World-EE/Java-Hello-World-Enterpris... is an excellent demonstration of this.
Your framing of the issue in terms of infrastructure projects vs. applications seems bizarre and simplistic. For example, one of the areas where Go shines is in highly concurrent, io-bound, networked services. Many examples of good use cases for Go in the wild: Kubernetes, CockroachDB, TiDB, etc.
https://www.cockroachlabs.com/blog/why-go-was-the-right-choi...
For infrastructure projects like PeerDB: Use Rust. It's significantly more performant out of the box, and allows you to use low level primitives like SIMD to make your project even more performant, which isn't possible in Go.
For applications, use Java or Python. The dev productivity is much higher versus a verbose language like Go. That matters more than the higher raw performance you might get from Go (for this use case).