4 ms·
the thing is it doesn't matter since a gem file and lock file will tell you what is the version of the library you are currently using. What is the version of
by aikah 11y ago
the thing is it doesn't matter since a gem file and lock file will tell you what is the version of the library you are currently using.
What is the version of the library go get has fetched one month ago ? you don't know ? and you will never know.
The problem therefore is not 3rd party libraries that can break. The problem is the tool go use to get dependencies doesn't help you with something like that.
Therefore all this "a version of a lib is a different lib" is a straw-man masking the real issue with go get. In every other modern language ,there is no such issue.
- brightball 11y agoIt matters because of inter-dependencies between all those gems. I'm not saying it's "the way" but Go's popularity is almost entirely due to solving problems that people experience in other modern languages. Dependency problems are one of those. Two gem needing a specific version of a common gem immediately bind their upgrade paths together for the life of your application. Without including version numbers in go get, it forces those 3rd party libraries to be backwards compatible. Some people like that.
- aikah 11y agoGo doesn't solve that, at all , in fact Go doesn't solve anything at all , thus the need for a proper package management solution in Go.