3 ms·
In short: they follow the Rust's approach. Great! Update: no, I'm wrong.
by nine_k 9y ago
In short: they follow the Rust's approach. Great!
Update: no, I'm wrong.
- TheDong 9y agoThat is inaccurate. In short, Russ Cox has been bashing cargo's approach of preferring newer versions and lockfiles and a SAT solver (or really an approximation of one). Apparently making the dependency-manager's code simpler is a goal worth removing developer's ability to be expressive and removing security updates.
- Conan_Kudo 9y agoI'd be surprised if the Go developers ever care to do this right. Google doesn't use any of this, and all their projects do extensive vendoring with heavy modifications (effectively forking them). Personally, I despise their approach to developing software, and on principle, I won't really develop software in Go because their attitude permeates through language and software development mechanisms.
- tcheard 9y ago> Apparently making the dependency-manager's code simpler is a goal That isn't the goal at all. The goal of Minimal Version Selection is to ensure that the version selected is closest to that which was tested by the app and its dependencies. > worth removing developer's ability to be expressive and removing security updates. And that isn't true either. It allows the developer of both the app and its dependencies to express the version they have tested against, and still allow the developer to receive security updates by explicitly increasing the version, allowing them to test that the update doesn't create problems while doing so. It allows for version pinning without the need for a lock file.
- notheguyouthink 9y agoI love Rust.. but isn't this approach very different from Rust? Rust doesn't even have the concept of import paths, which is almost entirely how Go is doing versioning here. Sure, they have verifiable builds, but even JavaScript (Yarn/etc) has had that for years.
- deleted 9y ago[deleted]
- mfer 9y agoThe approach is very different from Rust because of the minimum version selection. Instead of getting the latest version of a dependency it tries to get the oldest and this happens for transitive (dependencies of dependencies) where you have less control on asking for updates.
- mseepgood 9y agoDid you even read the linked article, his seven part blog post series on vgo [1] and the proposal [2]? [1] https://research.swtch.com/vgo https://research.swtch.com/vgo [2] https://github.com/golang/proposal/blob/master/design/24301-versioned-go.md https://github.com/golang/proposal/blob/master/design/24301-...