GC pauses might be an issue with Go (they don't matter that much in a Go server app, but in a client app like a browser things are very different).

I rewrote quite a bit of the Chromium browser in Go, achieving a 10x reduction in lines of code (I stopped this project before I could reliably evaluate performance). Since Chromium uses a multi-process model, this was pretty easy: I implemented the Chromium IPC protocol in Go (I wrote a Chromium utility to emit a JSON description of the IPC protocol), and then told the privileged and unprivileged Chromium processes to use my Go subprocess rather than the original logic. My Go logic ran on both Windows and Mac OS X.

Mind sharing if you have the code public ? :)

Belongs to my employer :(

Also, when I said 'quite a bit', I was thinking about the data-plumbing logic --- not UI and WebKit logic. It doesn't really make sense to rewrite WebKit.

Has Go got a good UI library?

It does not, and this needs to change before Go becomes viable for applications like this.

I had the same doubt.