The whole idea of tying image names to hosting provider urls or other kinds of locators was probably a bad idea. What if those things move to different domains

The whole idea of tying image names to hosting provider urls or other kinds of locators was probably a bad idea. What if those things move to different domains, or different directory structures? Wouldn't that break every Go program that depends on them? I've been using Java, Python, and Ruby for a while. They all have various pain points for managing dependencies but they do get one thing right: packages have names and versions, names are opaque strings that are not coupled to a particular hosting provider, and they don't care what directory on my laptop I use to store my dependencies and my code. The Go dependency model seems like a real step backwards in usability and maintenance. It's like they are forcing one software org's standards on the rest of us. We don't all work at Google! Just let us depend on things that have names and version numbers!