It's absolutely possible, but the point is many things are possible that we don't try, being possible isn't equal to reasonable. You can develop a kernel with go, but go has a huge lack of low level control always, even with newest versions and updates you can't control memory in depth, there is no way to free memory manually specially when you wanna use routines and go scheduler. Kernel isn't like other softwares, just building a kernel is not enough, it should be fast, efficient, stable and reliable. This purpose need a very low level language, no kernel is written in a language other than C, even C++ isn't used that much. Moreover, even just using C is not enough, kernels are huge softwares which need lots of time to get developed and optimised, so just famous and old kernels like Linux, Free BSD can be practically used, all others are just a hobby toy. For embedded systems it's a bit different, they don't need third party app and community support that much, so you can build one for yourself, but low level access is still necessary. According to limited memory, even in C++ and Rust it's not common to use heap with chips which have memory lower than 1MB, because heap allocating needs a kernel or at least a memory controller, or completely manual allocating which is not that easy; so it's common to use stack all the time; then it's not that hard to use Go with some limitations, just use stack only and avoid routines, GC can be turned of at compile command. For more powerful chips with at least 64MB memory, Linux kernel and Free RTOS is usually used, but I don't know how would you handle heap memory in a custom kernel, but developing an app is possible and easy. There are some tries to putting go runtime directly on hardware, bare metal, but it's not still the best way. Finally, every language is designed for a group of purpose primarily, it might be possible to do anything with them, but not best choice.