News for hackers. Stuff that matters.
Re:Confession From a Go Programmer by hdevalence on Thursday January 23, 2014 @12:25PM (#7109550)
What happens when the dependencies have bugfixes or security flaws? Why is it better to spread the responsibility for updates over all Go authors instead of to the authors of the libraries in question?
Re:Confession From a Go Programmer by nknighthb on Thursday January 23, 2014 @12:27PM (#7109572)
You make an explicit, knowledgable decision to update the dependency, like you should be doing with all software in a production environment.
Re:Confession From a Go Programmer by frowaway001 on Thursday January 23, 2014 @06:27PM (#7112217)
Why is this supposed to involve tons of stupid stuff instead of adjusting a version number accordingly?
Re:Confession From a Go Programmer by mseepgood on Thursday January 23, 2014 @12:30PM (#7109595)
> What happens when the dependencies have bugfixes or security flaws?

Copy the new version into the repository, run the import rewriting script and check it in.

> Why is it better to spread the responsibility for updates over all Go authors instead of to the authors of the libraries in question?

Because you want to have full control over your dependencies. What if the author introduces a breaking change or removes the repository from the internet? Do you want to risk your business by being at the mercy of someone else's repository?

Re:Confession From a Go Programmer by gmjosack on Thursday January 23, 2014 @12:40PM (#7109681)
What about when the library you want to use has a non-compatible license for distributing it with your source code?
Re:Confession From a Go Programmer by burntsushi on Thursday January 23, 2014 @12:33PM (#7109616)
Update them when you want. Just like you would with a package manager. If you need to stay up to date, then have something monitor their commit logs.