- Go makes it easy to write a process for your emulator, instead of a state machine.
- Go's slice types makes passing blocks of memory around a zero copy operation.
- Pass by value lets you reduce the number of objects GC must trace.
- Go is explicit about integer size and sign, makes conversion errors more visible.
It's not better than C, but it's certainly easier to work with. I'm routinely surprised at how C-friendly Go's produced code is -- take a spin through profiling some of the image library primitives and compare them against your favorite C library.
I used the same word three times because it may not hit any of those three bullet points 100%, if one wishes to build the fastest possible perfect emulator, but it's a decent starting toolset.
But if you claim that language X is good at Y, implicitly you're comparing it with all languages, not a subset. AFAIK most emulators are written in C or assembly or the like -- so it's especially odd to compare Go to everything but them in this context.
Perhaps I should have gone for the Monty Pythonesque "higher level than C but lower level than ASP.Net" term?