<story><title>Add opt-in transparent telemetry to Go toolchain</title><url>https://github.com/golang/go/issues/58894</url></story><parent_chain><item><author>kklisura</author><text>Can someone explain how we managed to have programming languages and toolchain development for half a century without using telemetry, but somehow we need it today in our tools? Their Why Telemetry? blog, just doesn&amp;#x27;t cut it for me [1].&lt;p&gt;[1] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;research.swtch.com&amp;#x2F;telemetry-intro&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;research.swtch.com&amp;#x2F;telemetry-intro&lt;/a&gt;</text></item></parent_chain><comment><author>estebank</author><text>Humans managed to live for most of history without penicillin, or even boiling water, at the cost of most humans dying before making it to adolescence. People managed to have global communications with only steam ships and telegraph, at the cost of slower pace of information dissemination. NASA managed to make it to the moon with less computing power than the cellphone in your pocket, at high resource, monetary, human and time costs. Cars managed to work with more rudimentary design than today&amp;#x27;s, without any computers, at the cost of lower life-spans, lower efficiency and higher pollution.&lt;p&gt;You can make many arguments for and against telemetry in developer tools. Not acknowledging that telemetry helps with visibility into how those tools actually work in the wild, which in turn helps lower the incidence of bugs and speed up development, is disingenuous. You &lt;i&gt;can&lt;/i&gt; arrive to the conclusion that even inert, opt-in telemetry is not worth it, but don&amp;#x27;t disregard out of hand the utility of it in helping their development as if it were some crazy idea.</text></comment>
<story><title>Add opt-in transparent telemetry to Go toolchain</title><url>https://github.com/golang/go/issues/58894</url></story><parent_chain><item><author>kklisura</author><text>Can someone explain how we managed to have programming languages and toolchain development for half a century without using telemetry, but somehow we need it today in our tools? Their Why Telemetry? blog, just doesn&amp;#x27;t cut it for me [1].&lt;p&gt;[1] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;research.swtch.com&amp;#x2F;telemetry-intro&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;research.swtch.com&amp;#x2F;telemetry-intro&lt;/a&gt;</text></item></parent_chain><comment><author>gjulianm</author><text>You can manage to have things without telemetry, but having telemetry is incredibly useful. I think the example of &amp;quot;how much of our user base actually uses these features&amp;quot; is a very good one, specially in a compiler where maintaining old features could be adding a lot of complexity to the code base. And, as they also explain, a lot of bugs and undesired behaviors are things that the users won&amp;#x27;t know they have to report and just accept as part of the normal behavior. Things like cache misses, slowed down compilation times in certain situations, sporadic crashes... All of those things could be improved if the developers knew about them.</text></comment>