‹ BackHN Continuity

Thread

Don't couple your Go code to GitHub

325 points · 177 comments · birdculture

  1. SenHeng · · focus · HN ↗
    GitHub is almost forever. Your custom domain disappears when you stop paying the bills, which if you’re an open source developer has a higher likelihood than GitHub disappearing.

    One day, we’re all going back to vendoring dependencies.

    1. otterley · · focus · HN ↗
      Why did we stop vendoring dependencies in the first place?
      1. st3fan · · focus · HN ↗
        I vendor all my Go dependencies all the time for every project. It is the way.
        1. throwaway894345 · · focus · HN ↗
          Has this ever been necessary/useful? Genuinely curious because I’ve been using Go since 2012 and can’t recall a time when vendoring solved a problem better than “regular” modules. Like have there been times when the source went down and the module proxy went down (or didn’t have your dependency cached)?
Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.