4 ms·

I'm amused... While this was on the homepage or hacker news, vgo was marked as accepted. It's the timing I find amusing. https://github.com/golang/go/issues/2

• kardianos 8y ago
  Yes, it is amusing that this objection to the vgo proposal are only now coming forward when it was proposed 2018-03-20, 2 months ago, and the design document a month before then.
  • sagichmal 8y ago
    Russ and the core team ignored the dependency management issue for years, and only responded to the community-led `dep` initiative after a year and a half. The `vgo` proposal was something like a hundred pages of dense technical details, and Sam has a full-time job. I think the sense of urgency you're implying is both artificial and unfair. It's been years already; we can wait another month or two for the details to shake out.
    • nemo1618 8y ago
      >The `vgo` proposal was something like a hundred pages of dense technical details Which document are you referring to? The one linked in https://github.com/golang/go/issues/24301 https://github.com/golang/go/issues/24301 is only about 600 lines: https://github.com/golang/proposal/blob/master/design/24301-versioned-go.md https://github.com/golang/proposal/blob/master/design/24301-...
    • geodel 8y ago
      > The `vgo` proposal was something like a hundred pages of dense technical details, and Sam has a full-time job Does that mean 2-3 months are not enough to read 100 pages document and respond specially from people who are most concerned about package management? Or that Sam should be the only one to respond to this?