‹ 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. collabs · · focus · HN ↗
        Because it sucks. But maybe it should suck? It would make us think twice before adding dependencies.

        I use dotnet and I never liked seeing dlls and binary files in my diffs. I would argue if we are adding vendor code to our projects, we should demand the FULL source code instead of dlls. Maybe it is already possible with things like x unit. I have never given it much thought... But then that vendoree code has to come from somewhere as well, right? I mean there is something to be said about provenance or something here?

        Sorry if this feels like a stream of consciousness because it is ↔

        1. otterley · · focus · HN ↗
          Vendoring dependencies doesn’t necessarily mean you have to include binary objects in your repo. They could be content-addressable artifacts in your org’s private blob store.
          1. someonebaggy · · focus · HN ↗
            i.e. they could be NIH git-lfs.
Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.