I think it's worth noting that Go HAS a garbage collector available, but it's entirely possible to write code which doesn't rely on it, at least in the user-wri

I think it's worth noting that Go HAS a garbage collector available, but it's entirely possible to write code which doesn't rely on it, at least in the user-written code. Furthermore, the compiler itself can help in the (re)writing of code to effect stack allocations of variables, avoiding runtime reliance on the garbage collector. This is effected, in general, through "escape analyses" that prevent reliance, at runtime, on garbage collection. Punchline is calling Go a garbage collected language can be entirely inaccurate, depending on the program being compiled.