That's exactly what the article I linked said, isn't it? It has low pause times, at the expense of everything else. Beware trading a visible cost for an unboun

That's exactly what the article I linked said, isn't it? It has low pause times, at the expense of everything else. Beware trading a visible cost for an unbounded number of smaller costs. In Go's case, in return for minimal pausing you get memory fragmentation, terrible performance if the GC is ever seriously taxed, and a 100% (!) heap memory use overhead. If you're just writing commandline daemons or servers you restart every ten minutes though, who cares? Go doesn't come off too badly in this because it's not Java, which allocates like crazy. That's a laudable tradeoff, but that does not mean they solved garbage collection very well.