What a ringing anti-endorsement. The author seems...retarded.

- Go is a good language for building websites/web servers.

Uh those are completely different goals, but lets see if we can see how he ties it together.

1. Databases: I wrote my own implementation in Go. (to file)

Just wow.

2. RSS Feeds: I wrote my own implementation in Go.

Of course you did, because Go's libraries have gaps. That's what you should have said.

3. S3/Zip: I use files, so this was trivial.

How is this a common problem (it isn't) and why did you mention it at all?

4. Deployment: Always difficult.

What is wrong with this guy.

5. Server Config: Standard.

Thanks for telling us nothing except that you split 3 webservices over different ports and tied them together on the same ngix webserver. That's not awkward at all. Wait, didn't we start with the statement that Go was suited for building webservers...nevermind.

Nowhere in here did I gleam why I would choose to use Go or even RISK it.