On a number of fronts, I appreciate this. When I was first assessing whether to get into Go, and as a team lead whether it would be fit for future efforts, som

On a number of fronts, I appreciate this. When I was first assessing whether to get into Go, and as a team lead whether it would be fit for future efforts, some of the questions answered on this site were some of the first I queried to see if the investment was worth it i.e. Why would I use this? Who is using this? What are they using it for? If I introduce this to my teams as a potential member of our stack, am I introducing something that will be niche and hard for others to pick up and maintain, or will this have multiple applications and thus foster greater adoption? I obviously could find the answers elsewhere and have since chosen Go for a lot of cases, but a clean one-stop-shop like this for others to look to, or be pointed to, when they first hear of the language is valuable (from my experience, and in my opinion).