Hacker News Reader

npm is just another layer on top of git. go uses git directly. how is that any worse?

From someone who briefly used 'bower', which was JS dependency management using git, relying on git is a lot worse.

Github repos can vanish, NPM will only let repos be deleted if they have no direct dependencies also on NPM. So you have some guarantees your dependencies wont vanish.

If the repo was used at least once, it will be cached by the default proxy. At that point, deleting it will have no effect on builds

Does go have some intermediate cache repository between github and enduser?

Yes, https://proxy.golang.org/

You can also configure go to use your own for internal projects or if you just want to avoid the global proxy.

Reply on news.ycombinator.com