an interesting project.<p>the size of the image concerns me:<p>kernel+boot 100MB, with C it could be 4MB.<p>kernel+boot+basicpackages 500MB, with C it could be 16MB.<p>Golang is designed to be static all-in-one packages for each application(e.g. microservices), when you run a lot of them in any given system, it becomes really large together.<p>I don't mind to use one or two go binaries in my embedded board, when I need a few of them, I am concerned about the storage size(possibly memory size as well).
Is this kinda like the Nerves approach but for Golang? (<a href="https://github.com/nerves-project/nerves" rel="nofollow">https://github.com/nerves-project/nerves</a>)
It took a bit of digging, but it seems that encrypted wifi is not supported:<p><a href="https://github.com/gokrazy/gokrazy/issues/13" rel="nofollow">https://github.com/gokrazy/gokrazy/issues/13</a><p>And if you read the issue, it's a bit understandable to not want to reimplement wpa_supplicant.
If you want to go deeper, there is also bare-metal Go runtime for rpi (among others): <a href="https://github.com/f-secure-foundry/tamago" rel="nofollow">https://github.com/f-secure-foundry/tamago</a>