3 ms·

I think most pathological cases can be reduced to similarly simple examples. I'm sure these exist for other GCs as well.

• stmw 9y ago
  Yes, the take-away here is not that Go is particularly bad, but that GCs are problematic. Notably, GC != automatic memory management.
  • littlestymaar 9y ago
    > Notably, GC != automatic memory management. Actually, GC == automatic memory management, just not automatic performant memory management
  • weberc2 9y ago
    That's not a reasonable conclusion to draw. You would need to preallocate to maximize performance regardless of GC in this case, and in other cases, the performance and determinism gaps between GC languages and non-GC languages is almost entirely due to tertiary factors. For example, GC languages are more likely to prioritize friendliness over raw performance in other areas--language features, compiler optimizations, standard library design, etc. Non-GC languages really only need to appeal to the high-performance and high-determinism crowds.