Or at least, the language resists the sort of ORMs that the web world has become accustomed to, with tons of convention-over-configuration and such. A more static one could probably be done.
I find myself wishing the "go" toolchain would give me a defined way of running certain code before the compiler, so I could generate Go code with the go source tools. From there you could easily compile yourself up some ORM code by examining a database at runtime. It's yet another privilege it claims for itself but gives you no way to hook into.
There is Revel, but it seems to be getting a bad rap ("non-idiomatic" label used as a stick).
Martini is still young (less than a week) but the core is pretty fleshed out.
No boosting here (I don't even have that many twitter followers). I just put together a framework that doesn't step on your toes and people ate it up :)
I don't expect everyone to agree with me surrounding Revel, but I certainly think it's lack of modularity is a negative.
https://groups.google.com/forum/#!searchin/golang-nuts/marti...
The Revel comment was more about a criticism I've read several times now.
I liked and bookmarked the article. :)