3 ms·
In this context, it would break a crap ton of Go modules, though. That’s the point, and git decentralization has nothing to do with it, unfortunately.
by christophilus 3y ago
In this context, it would break a crap ton of Go modules, though. That’s the point, and git decentralization has nothing to do with it, unfortunately.
- hnlmorg 3y agoAs some who writes a lot of Go and thus has actually had to deal with this problem already: the hard part is finding a new source for the module. Updating your project to point to the new module takes around two minutes tops. But finding that module is the hard part. However this isn’t a uniquely Go problem. You have the same problem when switching to a new module in any language and the reasons you’d struggle is the same: because the existing module has been abandoned. If it hadn’t been abandoned then it’s very easy to find the new git repo and thus update your Go project. > git decentralization has nothing to do with it, unfortunately. It has everything to do with it. You have a local copy of the repo on your development machine and thus can throw a new mirror up if you need to. All you lose is any issue tracking and existing maintainers. But if you’re having to resort to this, those maintainers have likely already abandoned that module already.