It feels to me like it's tying your code to something ephemeral. If you're going to do that you may as well make it something uniquely ephemeral. Github, Docker

It feels to me like it's tying your code to something ephemeral. If you're going to do that you may as well make it something uniquely ephemeral. Github, Docker Hub, Packagist et al use usernames for this, it works nicely, packages are namespaced in the form username/packagename. People advocating using a domain as the namespace get the same result, but the package namespace is tied to a domain, you have to have control of that domain, if you lose it, do you lose the namespace? What if I don't own any domain, people are saying in that instance I should use io.github.myusername, why not just myusername? that way my code isn't tied to a platform I may not use in 5 years time. I suppose that's it, a namespace is about my code, not about where the code is maintained or an external resource I may or may not keep access to, so don't namespace it in a way that ties it to such.