I've recently been looking at some new languages: Scala, Haskell, Clojure, Node.js etc. Go was the only site to put code samples (live ones at that) on their front page.
Language/framework creators take note: The first thing I want to see on your site is what the code looks like. How to install it is a distant second (I can look it up once you've convinced me it's worth installing)
Being open source is not a real advantage any more, but it takes so little effort to summarize your project at the top of the README, so please do it so I can fall in love with your stuff.
It may be a throwback, but it's still a good idea.
I'd also like to see a built-in IDE analogous to Python's IDLE to lower the barrier-to-entry. IDLE is great for education.
I also think that Go needs to establish some sort of independent entity for the future development of the language. People need assurance that Go isn't going to go away if Google gets bored with it. Go hasn't crossed that rubicon yet, and this is another big barrier to adoption.
I am always interested in getting people's opinions... and help. Most of the people who use Go however, including me sometimes, seem to use more lightweight text editors like vi.
$ hg clone -u release https://go.googlecode.com/hg/ go
$ cd go/src
$ ./all.bashWell played.
seems like they both got lost.
Checkout the usage for ./go so-far here: http://code.google.com/p/go/source/browse/src/cmd/go/script....
I discovered http://code.google.com/p/go-gb/ and haven't looked back. It makes building Go code SO much nicer. If I just want to try something quick in Go I just make a directory, place my whatever.go file in it, type 'gb', and run my program.
I really hope they make this 'go' tool as easy as 'gb'.
I develop primarily on a Windows machine, so this is some good news.
Close is intended as a way for a sender to signal
that no more values will be sent.
Go 1 will disallow close on receive-only channels.