I like not having to think about lifetimes and ownership when I'm building a tree for example, and for most of what I do I can afford the performance hit.
So i imagine you know this, is it the syntax you're trying to avoid? Ie wrapping a lot of things in RC's is annoying?
(Yes, GC tuning is painful, but better than rewriting code hoping you might end up with the same behavior.)
My big issue with Go's GC, or GC's in general, is consistency. Go's GC can still be variable in pause time iirc. But it's been ~3 years since i've worked in it - so maybe my memory is wrong :)
About the consistency, I think that's not a GC problem in general. For example, Java's ZGC has constant pause times: https://malloc.se/blog/zgc-jdk16.