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 p

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 https://research.swtch.com/vgo-intro [2] https://sdboyer.io/blog/vgo-and-dep/ https://sdboyer.io/blog/vgo-and-dep/