> "The developer should have done X!", well, then why doesn't Go just do it by default It _does_ do it by default; the problem in this case appears to be (alth

> "The developer should have done X!", well, then why doesn't Go just do it by default It _does_ do it by default; the problem in this case appears to be (although I could be wrong) that the developer went out of his way to do the wrong thing. As I've noted elsethread, I could be wrong; possibly he was misled by something else. But the default way Go handles dependencies is exactly the way one would expect: you code against one version of a dependency, and have to manually pull in a new one.