3 ms·
I swear I'm not trolling: what do you not like about modern golang's dep management (e.g. go.mod and go.sum)? I agree that the old days of "there are 15 dep ma
by mdaniel 2y ago
I swear I'm not trolling: what do you not like about modern golang's dep management (e.g. go.mod and go.sum)?
I agree that the old days of "there are 15 dep managers, good luck" was high chaos. And those who do cutesy shit like using "replace" in their go.mod[1] is sus but as far as dx $(go get) that caches by default in $XDG_CACHE_DIR and uses $GOPROXY I think is great
1: https://github.com/opentofu/opentofu/blob/v1.9.0/go.mod#L271 https://github.com/opentofu/opentofu/blob/v1.9.0/go.mod#L271
- geethree 2y agoTo be fair your specific example is due to… well forking terraform due to hashicorp licensing changes.
- mdaniel 2y agohcl is still MPLv2 https://github.com/hashicorp/hcl/blob/v2.23.0/LICENSE https://github.com/hashicorp/hcl/blob/v2.23.0/LICENSE and my complaint is that the .go file has one import path but the compiler is going to secretly use a fork, versus updating the import path like a sane person. The only way anyone would know to check for why the complied code behaves differently is to know that trickery was possible And that's not even getting into this horseshit: https://github.com/opentofu/hcl/blob/v2.20.1/go.mod#L1 https://github.com/opentofu/hcl/blob/v2.20.1/go.mod#L1 which apparently allows one to declare a repos _import_ path to be different from the url used to fetch it I have a similar complaint about how in the world anyone would know how "gopkg.in/yaml.v3" secretly resolved to view-source:https://gopkg.in/yaml.v3?go-get=1 https://gopkg.in/yaml.v3?go-get=1