Don't couple your Go code to GitHub
The author argues that Go developers should avoid coupling their code to specific hosting providers like GitHub by using custom vanity domains. This practice prevents vendor lock-in and simplifies infrastructure changes if a hosting provider is switched.
Why it matters
It addresses a common technical debt issue in software engineering, promoting better architectural practices for long-term project maintainability.
One of the good features of Go is that you namespace your code with the location to fetch the code. This means if you host your Go code at http://github.com/thetrueares/boneclone then you have the line import “github.com/thetrueares/boneclone” and Go will fetch it using git. This makes it super easy to know where to go to report bugs for open source libraries and really easy to fetch and distribute go libraries without a centralised package management system. For many, it’s literally the location of the git hosting, but this has some downsides, and you should use your own custom domain, and I’ll explain why.
Get smarter about the news
Sign up free for a feed built around what you actually care about, Dive Deeper research on any story, and the full text of every article.
Create free accountAlready have an account? Sign in