[feniv]

My experience has been pretty similar: Go is perfect for building high performance APIs. A lot of the library infrastructure is still in early stages.

One suggestion: Don't bog down your application server with serving static files (Slide 7. favicon and robots.txt). I put all of my css, js and image files in a /static sub-directory and configured nginx to serve any URL starting with /static without hitting my go-server.

[motter]

Thanks for pointing that out. The static routes in the talk are just for illustration -- we use nginx to serve them in production.

One thing I haven't touched on at all is html template rendering, something I'd like to take a look at in detail at some point.

Would like to hear more about your experience with Go -- is there a writeup somewhere?

[Herbert2]

Despite the overall ecosystem being rather small, the standard library and adjoining experimental packages are excellent. I wouldn't be surprised if go 1.2's stdlib would cover most of what Python's stdlib and Twisted can do.

[pjmlp]

> My experience has been pretty similar: Go is perfect for building high performance APIs.

Like any native compiled language, it is just a matter of having the right set of libraries available.