4 ms·

Arguably if Go had done this years ago, go.mod would not have existed and this would have an even bigger impact. Just like we'll rarely pick exactly the right

• varispeed 4y ago
  How one depends on another? To me it sounds these things are orthogonal.
  • masklinn 4y ago
    Because of time? How would you use go.mod when go mod does not exist?
  • room271 4y ago
    go.mod provides a way to introduce the new behaviour incrementally. The key point is the dependencies can (and already do) declare different go versions in their go.mod file. When everything is compiled, each module is compiled with the behaviour that applies to its own declared go version. So even if you update your go.mod go version to take advantage of this (soon to be) new behaviour, you can continue to use existing deps happily without worrying they will break.
  • heleninboodler 4y ago
    There's an ambiguity in the phrase "then go.mod wouldn't have existed." One way to read it is "then, as a consequence, go.mod wouldn't have existed" and the other is "then go.mod wouldn't have existed at that time." I believe the intention was the latter, whereas you're inferring the former.
• Ensorceled 4y ago
  > Arguably if Go had done this years ago, go.mod would not have existed and this would have an even bigger impact. I'm interested in the logical arguments that would support this. I can't think of any.
  • morelisp 4y ago
    Are you of the opinion that the version in go.mod existed many years ago, or that requiring a recent number in it won’t comparatively limit the impact? Both seem obviously false to me.
    • johnnypangs 4y ago
      I think they misinterpreted the word “existed” in this case. They took it as go mod would have never been made instead of go mod didn’t exist at that time.
      • Joker_vD 4y ago
        But that's exactly what that sentence says, isn't it? Otherwise it'd been "Arguably if Go had done this years ago when go.mod did not exist, this would have had an even bigger impact" or something like this?
        • masklinn 4y ago
          > But that's exactly what that sentence says, isn't it? No? > Otherwise it'd been "Arguably if Go had done this years ago when go.mod did not exist, this would have had an even bigger impact" or something like this? That’s a worst take on the same sentiment? I find your version a lot clunkier. The original sets a hypothetical stage and from that its conclusion, I think it flows better.
          • Joker_vD 4y ago
            > The original sets a hypothetical stage and from that its conclusion, I think it flows better. The stage is "years ago", and conclusion is "go.mod would not have existed and this would have an even bigger impact". My version re-arranges the sentence so that "go.mod not existing" bit is a part of the premise, not of the conclusion. Tense agreement in English subjunctive is hard. Especially for non-natives such as me: I do parse the original statement like that and just can't bring myself to understand it otherwise.
• apatheticonion 4y ago
  I mean, Go had vendoring and vendoring managers not unlike npm and it's node_modules. But a language more comfortable with change implies that change is more likely - not less likely. Given pretty much every modern language has some kind of dependency management utility - I'd be surprised if Go didn't end up with one