Don't couple your Go code to GitHub

Go's practice of coupling import paths to git hosting locations creates unnecessary vendor lock-in, forcing developers to change their code if they switch providers like from GitHub to GitLab. The solution is to use custom domains (such as go.company.org) that act as indirection layers, allowing developers to redirect to any hosting platform without modifying code or affecting end users' import statements.