The advice goes somewhat deeper than this. Design goals aside you really shouldn't get too clever with GCs as they are subject to change. If the GC changes (because of platform upgrades, or simply using different runtimes) suddenly your application can start showing strange or bad memory performance characteristics.

Either way a less controversial way to put the Go advice would be:

> If you must read the rest of this document to understand the behavior of your program, you are being untrusting. Don't use things you don't trust.

If you care about memory performance characteristics that much you really should be using a language that gives you control over them.

That's not to say that all GC advice is bad: good GC advice exists and usually sticks to the formal definition of a GC (an infinite memory simulator), instead of implementation details which, again, can change.