Agreed - if you're new to programming in Go, I'd recommend using the standard library (supplemented by Gorilla[0] once you get the hang of things).
If things start getting unwieldy as your app grows, you can always try out something like Revel, but by starting with the standard library (which already has a very clean web server built-in), you'll get a sense for the way things work "under the hood" early-on.
If you want to see how a Go web server built with just the standard lib + Gorilla looks, I wrote a simple sample application a while back: https://github.com/ChimeraCoder/go-server-bootstrap . The most verbose part is the oauth2 callback.
I should get around to updating it (it still even uses a Makefile! Eek!), but it gives the basic idea.
(Sidenote: When did Github stop supporting the ".markdown" extension instead of just ".md"?)
If things start getting unwieldy as your app grows, you can always try out something like Revel, but by starting with the standard library (which already has a very clean web server built-in), you'll get a sense for the way things work "under the hood" early-on.
If you want to see how a Go web server built with just the standard lib + Gorilla looks, I wrote a simple sample application a while back: https://github.com/ChimeraCoder/go-server-bootstrap . The most verbose part is the oauth2 callback.
I should get around to updating it (it still even uses a Makefile! Eek!), but it gives the basic idea.
(Sidenote: When did Github stop supporting the ".markdown" extension instead of just ".md"?)
[0] http://www.gorillatoolkit.org/