News for hackers. Stuff that matters.
Re:Go Run by pdonis on Thursday February 22, 2024 @12:01PM (#39469867)
Because I don't want the code I'm running to change out from under me when I tell it to run because some dependency got updated (or for any other reason, for that matter). That's a recipe for disaster.

Running the code is a separate step from determining what code I am going to run; the latter includes determining exactly what versions of all dependencies I am going to run. The two should not be combined.

Re:Go Run by codegeek on Thursday February 22, 2024 @01:12PM (#39470869)
But the versions are locked right ? Similar to what package-lock.json etc does. So whats the issue ?
Re:Go Run by pdonis on Thursday February 22, 2024 @03:01PM (#39472281)
If the versions are locked, then after the first download, nothing should be downloaded again unless I explicitly change a requirement and/or a version. So after the first time with a given set of requirements and versions, I suppose "go run" would be fine since it won't actually download anything.

But for that first time, I still want to separate the two steps, for the reasons I've given elsewhere in this discussion.