We (a group at the Institute for Systems Biology) use it for some cluster management software (http://code.google.com/p/golem/) that coordinates 10's of thousands of core hours most days. The consistency and compactness and fast compilation of the language make it a joy to work in and the concurrency features and packages for basic http and web sockets etc make it great for wiring up distributed infrastructure. The standard go packages for http are so much better then the python ones it isn't even funny.
We leave our processes running for months and memory usage stays quite low and stability good which is surprising considering the minimal time spent in development (note: we run on 64 bit linux). (Actually the other day I realized we had generated 24 gb log file because no one had restarted the master process in months.)
We still use other languages for linear algebra heavy things or things that benefit from a more complete webframework (in terms of both features and documentation) but I am hoping the go ecosystem develops in those areas.
We leave our processes running for months and memory usage stays quite low and stability good which is surprising considering the minimal time spent in development (note: we run on 64 bit linux). (Actually the other day I realized we had generated 24 gb log file because no one had restarted the master process in months.)
We still use other languages for linear algebra heavy things or things that benefit from a more complete webframework (in terms of both features and documentation) but I am hoping the go ecosystem develops in those areas.