There is an uneven distribution of power here that allows someone to write a blog post, create a very poorly received proposal, and have it be accepted after a concession, all over the course of a few months. Compare that to some of the other proposals with a ton of backing that have been frozen for years (like https://github.com/golang/go/issues/49085) due to the core team disagreeing with the direction.
Basically, there's a very obvious in group that has to pay lip service to the proletariat but otherwise can do whatever they please.
That's fairly true of many (possibly most?) programming languages with more than 100 users.
You can always fork an open-source implementation, but that's a lot less useful when it means your code is no longer compiler-compatible with other people's code. So languages tend to be run by some committee, and a lot of the popular ones have a Benevolent Dictator for Life or a small committee.
Guido was Benevolent Dictator for Life of Python until 2018. C++ is standardized by JTC1/SC22/WG21 (and Microsoft still has huge influence on it based on simply whether they decide or not to incorporate a feature into MSVC). Ruby is an ISO standard. Common LISP is an ANSI standard. Modifying a widely-adopted language in a way that will be seen by most users is at least as much "Can you work with those with the political influence to decide 'yes'" as "Is your recommended modification technically good?"
That sounds like our old nemesis: politics. Who holds control and how they exert that control is a very human issue that exists for every project in existence (modulo an outlier or two).
Telemetry is valuable for making decisions and identifying issues, so it's no surprise the group making decisions about the future of the project would welcome the proposal.
i read that thread, and TBH it looks like the issue was indeed rejected on pragmatic reasons.
Coming from a language that is slowly but surely trending to an "everything and the kitchen sink" PL (aka swift), believe me, i appreciate A LOT the care with which go team makes sure any new feature composes perfectly with the existing state of the language and doesn't add too much complexity.
Basically, there's a very obvious in group that has to pay lip service to the proletariat but otherwise can do whatever they please.