4 ms·
Yes, go decided to wait to let the various competing systems duke it out in much the same way that node.js left it out for a while. I use git as my dependency
by chisleu 9y ago
Yes, go decided to wait to let the various competing systems duke it out in much the same way that node.js left it out for a while.
I use git as my dependency management. I pull a specific version of a golang dependency and put it into my private git repository. Then i don't have to worry about someone's github getting hacked, repositories getting deleted, etc...
Those problems have all happened with npm and github in the node ecosystem. Go solves these problems by allowing you to decide on how to manage your dependencies.
- iends 9y agoThis is no longer true. The core team proposed vgo a few weeks ago, after the majority of the community solidified around godep.
- Keats 9y agoDo you also fork all their dependencies and subdependencies and fix the path in all of them? Otherwise you are still at the mercy of account/repo renames or deletions