I want to thank everyone who contributed to Go 1. We have over 200 external contributors, some of them quite prolific, and Go is better for it. Thank you.
From the very beginning, we knew that Go had to be an open source project, free for anyone to use, adapt, and improve upon. That's why we're so excited to have such great contributors.
Even though Go is designed to address the software development problems we have at Google - and is now used in App Engine, YouTube, and other places within Google - we understand that they are faced by many people and that for Go to be a true success, it must have the broader applicability and appeal required to stand on its own. That's why we're so excited to see companies like Atlassian, Canonical, Heroku, and Tinkercad using Go too.
We've understood from the initial launch that Go needed to be more than just Google's language. The front page of golang.org
has never mentioned Google and carries none of the Google logo or branding, and that is not accidental.
In some of the coverage of Go 1, I see it repeated that Go is dropping in popularity because TIOBE says so. This is not what I see. If anything the Go world seems busier than ever, with more mailing list traffic than I can read and some half dozen books out or out soon.
If you read TIOBE's methodology carefully , you can see why they think Go is dropping in popularity. They judge "popularity" by averaging result counts from different search engines for "<name> programming": "C programming", "Java programming", and so on. However, they have judged that "Go programming" has too many false positives, so for Go they use "Go programming" "Google", requiring both terms. In this way, TIOBE essentially ignores all the references to Go as an open source project. Requiring "Google" to appear with "Go programming" for a hit to count is like requiring "Bell Labs" to appear with "C programming" or "Sun" to appear with "Java programming". The pages that talk about Go programming and feel it necessary to mention Google are mainly news articles, not actual discussions of the language.
What we learn from TIOBE then, is that Google Go is fading in popularity. That's great: it means the open source Go - the real one - is winning.