Having a GC doesn't preclude you from leaking resources(file handles, textures, etc) and you're at the mercy of whenever the finalizer decides to run once the GC has determined it's time to free an object. Usually this manifests as your Java application humming along until you hit some GC threshold cliff and then perf/memory plummets.
I also can't enforce ownership in Java which drives me up the wall. Once you hand out a ref anything is fair game and calling code is free to add that ref to the root GC set so that it never gets freed.
The comparison here was to "easier statically typed languages" (likely with an implicit "that one is likely to consider for a project these days"), with Go and Java explicitly raised for comparison. It's perfectly reasonable to respond to that with "There's no null", without explicitly acknowledging that there's also other languages (even ones before Rust) that don't have null.
People keep repeating that the popular language/framework/library of the year has $feature without acknowledging that it's not a new idea. This creates hype.
In addition the explicit error handling (together with enum error types) allow the compiler to check that you have handled every error case.
Rust has enabled me to write programs that just don't contain bugs (after an initial testing period). This is certainly acheivable with other languages, but it involves a lot of discipline, writing tests, etc. Rust makes it easy.