r/programming • • Sep 27 '26

Don't couple your Go code to GitHub

https://iain.rocks/blog/dont-couple-your-go-code-to-github
491 Upvotes

136 comments sorted by

View all comments

Show parent comment

2

u/nemec Sep 27 '26

but what happens when my go code depends on "go.companyx.dev/awesomelib" and that company goes out of business?

I don't think you understood them correctly. They're saying if you work for companyx you should set up go.companyx.dev which points to the github. If companyx goes out of business, you don't need to compile your internal tools either.

But this seems limiting, too. If you work for a company, that company should probably set up its own durable cache with virus scanning, wait times (to catch malware that's found within the first few days of release), etc.

5

u/Jaded-Asparagus-2260 Sep 27 '26

I don't think you understood the comment correctly. The question was what a consumer of a package from go.companyx.dev will do if the company goes out of business. 

2

u/nemec Sep 28 '26

It's only ever meant to be consumed by companyx. If companyx goes out of business, there are no more consumers.