It deals with a lot of stuff for you (static assets, SSL, logging, etc.) and lets you focus on developing your application rather than re-inventing the wheel.
Would be a good idea to add in a section on configuring that type of setup.
Waiting to see someone do some detailed benchmarks on Caddy before I commit to it for production stuff, because I'm too busy and too lazy to do them myself and I have a while left on my paid TLS certs.
I mention Caddy because it includes LetsEncrypt and HTTP/2 out of the box — and is written in Go.
location / {
proxy_pass http://127.0.0.1:8088;
}
Usually things like serving images, css, automatically compressing them, automatically compressing other traffic, domain redirects, ssl, etc. Helps keep your application focused although I realize it can be tempting to just do all that inside of go since it's somewhat good at it.