Golang's dependency management can't be fixed. Cloud vendoring / relying on archive.org for stuff was like a secret JavaScript sin but here Go has it out in the open.

What is the deal? I don't want to bust open the internals of this language to see if it's fixable at a deeper level b/c it's non-portable (if I found a way to package artifacts, they'd have to be system-specific) -- so eventually, with my druthers, I'll land on Rust for this kind of thing I guess :/