Sure you can do embedded development with the .NET micro framework because there are embedded systems that don't have hard real time requirements.
If you're building a hobby robot with netduino, you might not care if you have guarantees about input response time--as long as the delays are usually small enough. But if you move beyond that, you're most likely going to need a real time system.
http://www.atego.com/products/atego-perc-pico/
As a language I am not a fan of Go, but on the context of using strong type languages in embedded scenarios. I think the less C the better.
Just like JavaScript JITs, it is always a matter how much companies are willing to invest to improve the quality of the existing eco-systems.
So sure, if you want to use go syntax and build a completely new runtime designed for use in real time systems then go ahead.
As for strong typing in embedded scenarios Ada's been doing that for decades.