3 ms·
i recall there being some whining over go and "systems programming", but this seemed to hinge on definitions. go may not be the right option for a kernel but i
by abiox 10y ago
i recall there being some whining over go and "systems programming", but this seemed to hinge on definitions. go may not be the right option for a kernel but it's great for servers, infrastructure, platforms and various related things.
- tmccrmck 10y agoSystems programming is a vague term but it usually refers to low latency software (e.g. kernels, browsers, OS's, embedded, databases, etc) which means anything with a garbage collector is out of the question.
- abiox 10y agothat's just the thing: "anything with a garbage collector is out of the question" seems limited to a particular camp.
- teamhappy 10y agoSystems 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.