"Now that Google has released a stable version, and is deploying support on Google App Engine, it's likely to gain even more traction."
I think what Go actually needs is another popular framework so that the language can be used without depending on Google's App Engine and it's unstable pricing.
The great thing about Go as a web language is that alot of the bones are already there - templates and HTTP handling are already waiting for you in the standard library.
The most popular web frameworks i've seen for Go so far are Web.go (a Web.py clone) and Revel (a Play clone). Frameworks will develop organically over time. The only reason they're not very strong at this stage is because as I said; most of the batteries you need for web development are already included in the standard library.
> The most popular web frameworks i've seen for Go so far are Web.go (a Web.py clone) and Revel (a Play clone).
Unfortunately both web.go and specially Revel were developed by people that were not (yet?) familiar with Go's style, and they simply cloned what they expected from other languages and frameworks they were more familiar with.
Gorilla[1] and pat[2] (by the creator of Sinatra, who is now a Gopher) fit much more with the Go style and philosophy.
App Engine pricing stayed the same for years, then made a big shift as it officially came out of preview. Yes, it was a big change, but it's only happened once.
I'm a novice developer using App Engine and while there are things you can criticize about it (including the cost), "unstable pricing" isn't one.
I don't dislike App Engine. I just don't want to depend on it.
I don't like the idea that I am practically forced to use App Engine if I choose to use Go, since there aren't any viable alternatives as far as I can see. We need the "Django" of Go.
I think what Go actually needs is another popular framework so that the language can be used without depending on Google's App Engine and it's unstable pricing.