Hacker News Reader

Only in very bad implementations of GC.

By that definition, Go has very bad GC. Many (myself included) would strongly disagree with this.

Every memory management scheme makes trade-offs (even manual ones), and golang's is no different. It seems to work well in many scenarios.

It is better to scan everything than to copy it.

The op, most likely, was referring to generational GCs. Golang notably doesn't have one.