News for hackers. Stuff that matters.
Re:Go best practices, six years in (2016) by pjmlp on Friday March 02, 2018 @10:43AM (#16502343)
Well, it is on its way out, have you missed the news regarding vgo?

https://research.swtch.com/vgo

Re:Go best practices, six years in (2016) by chimeracoder on Friday March 02, 2018 @12:49PM (#16503900)
> Well, it is on its way out, have you missed the news regarding vgo?

Dep will have a clean migration path to vgo, and the latter isn't really production-ready yet.

For now, I'd recommend using dep for daily use, until you have a compelling reason to switch to vgo, at which point the migration will probably be automatic.

Re:Go best practices, six years in (2016) by kitd on Friday March 02, 2018 @10:48AM (#16502405)
Er, thanks. We've just moved to go dep :)

Go's dependency management story is starting to resemble JS's modules story :(

Re:Go best practices, six years in (2016) by dilap on Friday March 02, 2018 @10:52AM (#16502472)
Yeah... In defense of the Go folks (1) they are working hard to make the transition as smooth as possible (2) dep was always just considered an experiment (though with aspirations by the author to have it become the official solution) (3) vgo almost certainly marks the end of the churn, and looks really nice.
Re:Go best practices, six years in (2016) by allover on Friday March 02, 2018 @05:47PM (#16506475)
> Go's dependency management story is starting to resemble JS's modules story

It's worse tbh. npm was actually always usable if you knew what you were doing. Complaints with npm were generally down to misunderstanding, people not being aware of features like 'npm shrinkwrap' (which has now been replaced with a lockfile-by-default strategy) and of course registry issues (allowing unpublishing) that weren't unique to npm, and were only an issue for people relying on public registries at deploy-time, a bad idea.

Re:Go best practices, six years in (2016) by lobster_johnson on Friday March 02, 2018 @01:27PM (#16504283)
vgo is at least phrased as being a proposal, not necessarily the future of Go [1]:

    This post sketches a proposal for doing exactly
    that, along with a prototype demonstration ...
    I intend this post to be the start of a productive
    discussion about what works and what doesn't.
    Based on that discussion, I will make adjustments
    to both the proposal and the prototype, and then 
    I will submit an official Go proposal, for
    integration into Go 1.11 as an opt-in feature.
Of course, this is Russ Cox, so chances are that his proposal will carry more weight with his fellow core Go team than that of Dep's authors.

Sam Boyer's follow-up is interesting reading [2]. I get the feeling that despite their ongoing discussions, the Dep team was/felt ambushed by this move.

[1] https://research.swtch.com/vgo-intro

[2] https://sdboyer.io/blog/vgo-and-dep/

Re:Go best practices, six years in (2016) by vorg on Friday March 02, 2018 @04:39PM (#16505980)
The distrust of anything "not invented here" is prevalent in big corps like Google.