On the other hand, deprecating a critical tool of infrastructure leaves a sour taste. Many people would be pissed of. Better not including it in the first place.
IMHO such tooling should not be part of the language itself, and be left to the community.
I strongly disagree with this. "All batteries included" is one of Go's strongest points, especially if you look at gofmt, which set a standard for all code out there.
In more practical terms, I expect this tooling is provided and evolved as a first class affair because Google needs it internally to build their golang projects.
But I still prefer to have the occasional churn when "the official way of doing things" changes to having x competing tools doing the same thing, which has the potential of generating even more churn.
It's already making FOSS less accessible to people who are not developers.
Not to mention how quickly it rots.