3 ms·
Go's garbage collection probably looks like it "just works" because the type of person who, in 2016, runs into a GC problem on Go will probably just rewrite it
by jerf 11y ago
Go's garbage collection probably looks like it "just works" because the type of person who, in 2016, runs into a GC problem on Go will probably just rewrite it in Rust, rather than spend tens of thousands of dollars on a nonexistent best-of-breed Go compiler, the way you have that option for Java. So I don't think there's a lot of chatter about GC problems. There is some, but I think there's been more "I had a GC'ed language and switched to Rust and WOW! It was more work to write but the performance is blowing me away!"
Go does have a couple of structural advantages over Java, such as shipping with "value types" on day one, and it's good enough for many uses. But that's probably not accurately described as "just working" in that sense.