Too Long; Didn't Read
So recently <a href="https://twitter.com/_rsc?lang=en" target="_blank">Russ Cox</a> gave a talk at <a href="https://www.youtube.com/playlist?list=PL2ntRZ1ySWBdD9bru6IR-_WXUgJqvrtx9" target="_blank">Gophercon </a>about <em>“</em><a href="https://www.youtube.com/watch?v=0Zbh_vmAKvk&index=4&list=PL2ntRZ1ySWBdD9bru6IR-_WXUgJqvrtx9" target="_blank"><em>The Future of Go</em></a><em>”,</em> and he mentions that in order to get <strong>X</strong> feature in Go, we must first show enough <em>examples </em>of why<em> </em><strong>Y</strong> its a problem, so it gets attention from the Go team, helping them understand our <em>(the community’s)</em> point of view, we need to convince them that <strong>Y</strong> is a real problem and that <strong>X </strong>is <em>probably </em>the best possible solution.