Go's GC uses the same trick, and also shows a giant virtual size.
But you're right more broadly, it's nice to not have bad performance be a bunch of finger pointing between dev and ops with Go. With Java there's always another, untried GC twiddle to fix everything.
> With Java there's always another, untried GC twiddle to fix everything
That hasn’t been true since.. forever. If you have GC problems with Java, you are doing something stupid in 99% of the cases that can be easily fixed by any kind of profiler. That’s not true for most other GCd languages.
But you're right more broadly, it's nice to not have bad performance be a bunch of finger pointing between dev and ops with Go. With Java there's always another, untried GC twiddle to fix everything.