Systems programming is all about control. That usually means being able to control which instructions are emitted by the compiler and being able to control how

Systems programming is all about control. That usually means being able to control which instructions are emitted by the compiler and being able to control how things are laid out in memory, but it also means being able to control what happens when; and Go doesn't let you do that. If you can't guarantee that the function that's supposed to turn the reactor of when the temperature is too high finishes in time then that's a deal breaker. I think some people define systems programming as "interacting with the OS all the time"; which is something that Go is really good at.