News for hackers. Stuff that matters.
Re:Go is still not good by zozbot234 on Friday August 22, 2025 @09:28AM (#44984433)
Golang is great for problem classes where you really, really can't do away with tracing GC. That's a rare case perhaps, but it exists nonetheless. Most GC languages don't have the kind of high-performance concurrent GC that you get out of the box with Golang, and the minimum RAM requirements are quite low as well. (You can of course provide more RAM to try and increase overall throughput, and you probably should - but you don't have to. That makes it a great fit for running on small cloud VM's, where RAM itself can be at a premium.)
Re:Go is still not good by gf000 on Friday August 22, 2025 @10:29AM (#44985128)
Java's GCs are a generation ahead, though, in both throughput-oriented and latency-sensitive workloads [1]. Though Go's GC did/does get a few improvements and it is much better than it was a few years ago.

[1] ZGC has basically decoupled the heap size from the pause time, at that point you get longer pauses from the OS scheduler than from GC.

Re:Go is still not good by Capricorn2481 on Friday August 22, 2025 @11:36AM (#44985882)
Do you have a source for this? My understanding is Go's GC is much better optimized for low latency.