2 ms·
Does anybody have this wrong feeling about importing modules from some 3rd party URL (github.com in this case). I mean, if it is a one shot script, fine. But, d
by zerr 12y ago
Does anybody have this wrong feeling about importing modules from some 3rd party URL (github.com in this case). I mean, if it is a one shot script, fine. But, don't you plan this software to live 5 or 10 years after publishing?
E.g. imagine if phpMyAdmin had some critical imports from geocities.com...
I see it is common in Golang, so somebody please explain why don't you feel wrong about this.
- INTPenis 12y agoI think the reasoning is that it's development, and in a very rapidly evolving ecosystem. Once you ship a product you should obviously bundle and maintain the libraries you use with something like docker.
- kitsune_ 12y agoWith go, you should absolutely vendor your dependencies. Unfortunately, the tutorials and docs on their site do not point that out strongly enough, I guess a lot of beginners will be bitten by this in the future.
- forgotAgain 12y agoYou download and install the source locally. The import statement shows github.com because that is the local path into the local src directory. Using github.com in the local path is the suggested naming convention. You have the code so worse case you update it yourself.