4 ms·
Go technically would of been immune to such an attack unless of course they took down the project's github repository, but it's possible to host your Go code an
by giancarlostoro 11y ago
Go technically would of been immune to such an attack unless of course they took down the project's github repository, but it's possible to host your Go code anywhere with git or other VCS. One thing that I always loved about Go was this altogether.
- ngrilly 11y agoExactly. People have been laughing at Go for advocating vendoring. Now we have a very concrete evidence that this is a sane approach. The vendoring mechanism advocated by Go is better than a central registry (like npm, PyPI, RubyGems or crates.io). crates.io’s FAQ claims that a central registry is good for discoverability (find popular packages) and speed (fetch only necessary data instead of the whole git repository), but a proxy could provide the same benefits to an ecosystem based on decentralized repositories and vendoring.
- diggan 11y agoNot saying that NPM is perfect but you can host your node modules wherever you want as well. Supports tarballs/folders/git out of the box.
- giancarlostoro 11y agoIf that's the case, then why don't the users of that package update their dependencies to his github repositories? I know it sounds like a pain, but users shouldn't be so reliant on a service that could one day disappear, which is one reason I like Go's approach.