Comment by cogman10

As someone that likes GCs, I understand it.

GCs have a lot of tradeoffs involved. It's impossible to check all boxes and that means that there's going to be something to gripe about.

If you want your GC to be memory efficient you are likely trading off throughput.

If you want your GC to allocate fast and avoid memory fragmentation, you are likely over-provisioning the heap.

If you want to minimize CPU time in GC, you'll likely increase pause time.

If you want to minimize pause time, you'll likely increase CPU time doing a GC.

All these things can make someone ultimately hate a GC.

However, if you want a programming language which deals with complicated memory lifetime (think concurrent datastructures) then a GC is practically paramount. It's a lot harder to correctly implement something like Java's "ConcurrentHashMap" in C++ or Rust.