Go is portable... you just need to compile on the target. Go is write once, compile and run everywhere. Compiling would be part of the app install process; Compiling Go is much lighter than compiling C anyway.

NDK also lets you compile one binary for all device architectures now as well.

I think Google should require every app that uses the NDK to provide ARM, x86 and MIPS binaries.

Compile on install? Compile to something else then compile to binary? PNaCl?

I would go with "compile on install"

Google should've never cared about making Android work on x86. The ARM environment is an order of magnitude more competitive than the x86 one. So it's not like they need it for the "competition". If they'd like to have Android on PC's eventually, well they don't have to worry about that either, since ARM is disrupting Intel anyway, and will be the architecture of the future, being pushed by both Android and iOS, the most popular platforms right now (and even Windows is promoting it, although in a smaller way).

There are MIPS android devices too, I have one and it works well except when people write junks of their app in C and didn't upload the MIPS binary. Maybe with the recent POWER announcement we will see POWER devices.

Make Dalvik/JVM a compile target for Go? There is at least one project working on this.