Right, but I was thinking of Golang as an optional language that you could use to build parts of your app - the ones that require concurrency, performance etc. and can leverage Golang's strengths. So instead of writing C/C++ you would write Go code. You would still use Java for the UI part - that's not bad at all - you have memory safety, maturity, Garbage Collection and some time later even some of the cooler JDK8 features. No point in throwing all that away.

For that usecase may be Google can extend ART to convert Go code into something that plugs into the ART and outputs something that can be mixed with the AOT compiled Java code.