Тут у нас срач во имя императора о том, какой ужасный гц в го, ктоб мог подумать. Но вот 1 комментарий имеет зерно смысла:
A) Higher CPU usage for more concurrency and simplicity was a fundamental choice they made when designing Go's GC.
B) This benchmark measured the total time needed to complete garbage collection. But the program isn't blocked for that whole period. Usually it is only blocked for a few nanoseconds. The vast majority of developers will never have to even think about how fast the GC is.
C) A normal Go program would never have so many pointers. And if you're worried about using too many, it is much easier to avoid them than in a language like Java (there are other benefits to avoiding pointers, such as fewer cache misses).
D) Go is not intended to be the fastest language available. It is for people who want something that isn't horribly inefficient (like Python or Ruby) but also want something that tends to produce easy to maintain code. If you want the best possible performance, don't bother tweaking the GC, just use C++.
(
https://www.reddit.com/r/programming/comments/a9gej5/avoiding_high_gc_overhead_with_large_heaps/ecjp1kv/) #go
А еще забавно смотреть, как люди пихают gcless языки, не разобравшись в контексте. Да, я про раст))