It does look like the vendoring stuff is only there to satisfy backwards compatability, not for new usage. It's supported but now I've gone to look there are some caveats in the docs and on the wiki, hinting that you shouldn't use it. Files in vendor are ignored it seems unless you pass a special flag, so a lot of people are going to be very confused (including the author of this article). The communication around this tooling change have not been great, and that's why guides like this are springing up. Now that it is getting more complex, Go could definitely do with some more short and simple getting started guides from the Go team, for specific topics like versioning, where people also bring in their assumptions about how things work from other tools.
Since this is still in beta, and seems pretty half-baked, I'm not going to touch it for at least another version of go, but hopefully once they have the kinks worked out it'll be a reliable method to specify dependencies that everyone uses.
Go modules are fare simpler than what we had before - $GOPATH, vendor dirs, dep etc.
I have been using modules on a daily basis couple of months no and found it to be solid and intuitive.
Having used modules for a couple of months now on programmes of various size and complexity,
I would say that I am quite surprised by your claim that this is "still in beta, and seems pretty half-baked".
Could you give some examples to back up your assertion that it is "still in beta", and could you
give some examples to show which aspects of modules you consider half baked?
My own experience is that modules is an extremely well thought out and solidly executed solution to a problem which has
plagued the Go community for many years. Removing the GOPATH and the vendor directories, while providing repeatable builds make life as a developer much simpler. So don't stand aside. Join the party!
Nooo!! Don't tell people to run go mod vendor!
There is plenty of good docs around.
Have a look at https://github.com/go-modules-by-example/
Go modules are fare simpler than what we had before - $GOPATH, vendor dirs, dep etc.
I have been using modules on a daily basis couple of months no and found it to be solid and intuitive.
Having used modules for a couple of months now on programmes of various size and complexity,
I would say that I am quite surprised by your claim that this is "still in beta, and seems pretty half-baked".
Could you give some examples to back up your assertion that it is "still in beta", and could you
give some examples to show which aspects of modules you consider half baked?
My own experience is that modules is an extremely well thought out and solidly executed solution to a problem which has
plagued the Go community for many years. Removing the GOPATH and the vendor directories, while providing repeatable builds make life as a developer much simpler. So don't stand aside. Join the party!