What actually made a difference, for me, was changing my work. My dad experienced this too. If you're depressed maybe you need to change your life, this is hard. It was for me.
It jelled with what I know anecdotally. Their Indian outsourcing is terrible, bad compensation, nothing close to Google or other tech companies in India. This is from a few years back.
What's bad about his benchmarks? I've cursory glanced at them before and didn't notice anything in particular (used to write gpu drivers for a living).
You're right, the comparison isn't as valid as I thought, rustfmt has improved impressively since I looked at it last. 'go fix' might be a better comparison, what's the Rust equivalent?
I should have been more specific by tooling. I meant source code manipulation and analysis, go-oracle and goimports are a couple. There's many more in the go community.
Are they useful, I'm not sure. They feel useful but I have little trust in my judgment. When I switched back in the day from VS to emacs I didn't seem to miss all of the refactoring tools VS provided.
I'm thinking more of difficulty in writing rustfmt compared to gofmt. There's other examples like go-oracle or goimports which as far as I know don't have Rust equivalents.
How useful the extra tooling is, I don't really know.
There isn't one language to rule them all. An advantage of Go over Rust is easier tooling due to a simpler language, an advantage of Rust is a richer type system. These are in opposition.
Some history might help. Go was created largely as a reaction to writing server side C++. I have sympathy after writing but mostly reading C++ code bases. I swore never again.
I react in horror to the features being added to CUDA and SyCL to make them closer to C++.
I still hate C++ with a passion, grepping around in gecko is much harder than servo.