‹ BackHN Continuity

Thread

Don't couple your Go code to GitHub

325 points · 177 comments · birdculture

  1. thih9 · · focus · HN ↗
    > In my opinion, every commerical software development team using Go should be using custom domains for namespacing their internal libraries and packages.

    I’d remove “go” from the above, i.e. I think same applies to other stacks.

    Even using GitHub domain links in code comments gets problematic long term. Ie when a migration happens and those links start pointing nowhere.

    1. throwawayffffas · · focus · HN ↗
      I don't love that either, having all of your stack point to your own domains for how it can be accessed is nice. But in my opinion, it's desirable to be able to build your whole stack from source code. Of course you download external dependencies, but for code you own you should be able to build it from source.

      I have seen too many cases of requirements on internal projects that prohibit devs from working because oops the vpn is down now or oops gitlab is under load and the pipeline for your dependency won't finish for the next hour.

      1. bayindirh · · focus · HN ↗
        I also think that vendoring or at least caching your dependency tree somewhere local, so you can build everything from ground up to a known state.

        It's not only an issue of availability or depending on circumstances you can't control, but a matter of reproducibility hence dependability.

        I want to be able to compile critical software when a zombie apocalypse hits, and I have a growing discomfort about trusting outside parties for their availability and benevolence.

Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.