Golang won't work for these cases. A garbage collector is like a layer on which the rest of the program runs. It's very unstable to bootstrap the GC in an OS kernel BEFORE the kernel runs. Aka you need a kernel first to run a GC, and with Golang you will need the GC first to run the kernel. Similar thing applies to many other systems, the extra GC layer is a continual pain point.
And I would also wanna add that Go is very very use-case-specific to Google-like products (scalable solutions made by tech gaints like Digital Ocean or Docker).
I'm preatty new to Rust, so the obvious question (for me) is: "why Rust over Golang in these cases"?
Golang won't work for these cases. A garbage collector is like a layer on which the rest of the program runs. It's very unstable to bootstrap the GC in an OS kernel BEFORE the kernel runs. Aka you need a kernel first to run a GC, and with Golang you will need the GC first to run the kernel. Similar thing applies to many other systems, the extra GC layer is a continual pain point.
Besides what @nielvandw and @buinauskas have already mentioned.
Before writing the post, I've done some research and found that Rust and Go are not competitors.
And I would also wanna add that Go is very very use-case-specific to Google-like products (scalable solutions made by tech gaints like Digital Ocean or Docker).
AFAIK Rust is faster and is designed to be a systems programming language.
Go, on the other hand, is designed for microservices, web based tasks for high concurrency, easy vertical and horizontal scaling.