justforfunc #42: Intro to Go Modules and SemVer 

I have read many articles on go modules but couldn't got clarity. After watching this video, its totally clear and i have understood the concept. Great video as usual.

Awesome, Francesc. I had no time to look at the proposal and in just 30 min you explained how Go Modules work. Thank you!

Very helpful seeing the errors along the way and how to fix each step. Super stuff!

Dramatic look gopher, made my day !

simple y práctico! I've read articles about go modules but with this explanation I've understood it definitely. Thanks for the video

This was so useful! Thanks, Francesc!

this channel very good when explaining about go modules.

Great video and introduction! Added a link to this video on the Go Modules wiki page in the Introductory Material sub-section. :-)

Thanks for the video, really clear explanations !

Love Your Every Video :-)

Thank you. This is by far the best tutorials on go on youtube. Would you be able to address on how to handle when a git repository is removed, force pushed or renamed. More interested in knowing the good practices that we can follow. Like pushing the vendor folder, keeping a local copy of module somewhere?

Thanks for great videos, keep it up :D

the best golang channel.

This was very useful, thanks !

Very good explanation, thank you!

you are a beast man, great work

Thank you so much. It is so helpful.

Very informative. Please keep it up

this video still relevant in 2021. thanks.

Thanks for this Video. I started with go in August 2018 (go 1.10) and read / watched as much as possible about the history of go. I've read the blog post about "go modules", some more Webpages and watched diffrent Videos about it - Same for SemVer. You bring everything to the point. I'ved development my Adminscripts and some small apps not in GOPATH. Since they were small enough I didn't had trouble with GOPATH at all. I'm in a portable enviroment so I have to use on a network share and set GOROOT = GOPATH (Didn't know it better at that time). I should have splitted it in the first place anyway, cause Versionupgrades are more complicated. But go modules to the rescue, I won't be bothered with it anymore. Currently I think I will stay with the method to have every project in independent directories. I asked my self if it is still a good Idea to split GOROOT and GOPATH cause of the modulecache GOPATH/pkg. What do you think ?

Thanks for this introduction to Go Modules! You earned a subscriber. I am currently using Dep and am waiting for the stable Go Modules version of before I migrate all my projects. Can I suggest that if it's not too troublesome, publish the major subject timestamps in the description? I wanted to skip directly to the Go Modules part because I'm already familiar with SemVer. BTW it's awesome the way you pronounce "module" :)

Thanks!

thanks great video

29:27 you can just do: «grep -R *» and it will have the same result, but it's quicker to type.

Hi Campoy! Thanks for your video. With modules, is still possible having the vendor directory to commit all dependencies?

So this is the "official" version of vgo? Thank you for another quality video!

Finally we have hermetic builds!

this was really helpful! i tried reading golang modules doc but found it too dense for a noob given a "legacy" codebase just trying to add and test a small piece of code.

i think i'm falling in love

This is cool. Great video on a much needed feature. Would it be a best practice to check in the go.sum file as well?

Thanks for the video. I didn't understand if modules are a best practice or should be used only if you have dependencies? For example if I have a simple script, that uses only built in Go packages - do I need to use modules?

How does it solve dependency conflicts, like depending on different version of the same thing? Or each module is an island on it's own?

Interesting to see that while Go package versions should start with "v", Go itself does not seem to start with "v". When you typed go version, it printed "go1.11.2".

Is the vendor directory updated when you update your dependencies? or do you have to run `go mod vendor` again?

Both golang and node.js had the same problem in versioned dependency resolution. And it looks like go borrowed heavy inspiration from node as both maintain hash to point to the dependency version. It's package.json and package-lock.json ressemble go.mod and go.sum files here.

Awesome and helpful video. Thanks! @23:25 when cloning embedmd, the latest version actually already contains go.mod and go.sum, just FYI.

How would this work with an api codebase? Do I still use modules for the bigger Go codebases or are they only for packages/libraries?

Do I still need to use Go modules if I'm just creating a standalone application (so no outside imports) living inside gopath? Or should I do that as a best practice?

If you do another vide on modules it might be worth mentioning that backward compatability doesn't count for v0.x.y. I hadn't really heard it said much and it came as a suprise when I first heard about it.

Excellent Tutorial. Phantastic Speaker! Let me know where I can donate some bucks!

How to correctly change module name and repo it is stored ? For example if I want to start with github and then replace with gitlab

Thanks for the video! Not sure to understand the last part with the S/sirupsen issue, I was expecting some magic there but in the end you have to manually change the import in the vendors, so what's the point?

Thanks, please review gorm vs other vs native

is dep going to be replaced by go.mod in the future ?

Thanks! this is a great explanation (and demonstration) about that concepts. 29:30 You may also use grep -r github.com/Sirupsen/logrus **/*.go

Just wondering how going outside GOPATH will affect using guru. Does guru find imports that are outside GOPATH?

so this is like a more obfuscated and complicated implementation of rust's cargo?

Great video! Very quick follow-up questions: 1. Can your go module depend on non-modules (i.e. they don't have go.mod)? In other words, can you depend on something that isn't semantically versioned? 2. How do you set the semantic version of your module? Through git tags? In go.mod?

My package exists at [/root/go/src/myProj/drivers/myPkg] in GOPATH (/root/go) I am importing it in /root/go/src/myProj/myComponent/xyz/abc/server.go but I get the following Error: package myProj/drivers/myPkg is not in GOROOT (/usr/local/go/src/myProj/drivers/myPkg) Why is it not checking the GOPATH location?

:( stepping into bit more advanced workflow and found all this go modules thing bit confusing. Like... i am working on some nested module (monorepo) in separate branch... made some protobufs, later updated those and then in the same branch i want to use those updated protobufs, but i can't because my imports are pointing to previous version of protobufs. Its just becomes really messy to keep in head all this stuff.

Hi thank you for the video it was quite informative . Currently we are using go with oracle. We are using go-oracle which uses C code, I know mod does not copy the non-go code in the vendor directory. Due to this my compilation breaks. Is there a way to handle such a situation?

How to use a dependency which doesn't use go modules? Can I specify "latest" in go.mod for one of my dependencies?

Looking for a video on syscall. How those systemic specific packages went out of go main repository. How to rightly use them? And an example of cross platform build (mmapped i/o on linux vs windows).

Hey. Is it possible to use versioning in import block? For instance package pack1 import ( "github.com/noname/superpac v1.2.3" ) package pack2 import ( "github.com/noname/superpac v1.4.3" ) package pack3 import ( "github.com/noname/superpac v2.2.3" )

If i create a module with name foo and upload that to github.com/ehsanranjbar/bar How should i import that and how go mod can find repo?

I'm confused. semver.org/spec/v2.0.0.html says nothing about "v" prefix. It seems to me that "v0.1.0" is not semver compliant, but "0.1.0" is.

Lmao this guy loves golang

How do modules work with cross-dependencies? For example, if I am using foo/goofy and bar/mickey, and they are both using mylib/common but with different version of it? Probably the "not vendored" version could work since they are probably referencing different things under the pkg/mod directory, but how the vendor folder will be?

Hi Francesc, you say in the video that you would be happy to run your workshop in a conference. I'm part of RivieraDev organizers and I would like that you apply in the CFP for a Go workshop. How can I get in touch with you to talk about this ?

I dont really understand why we still need to use "go get something". How about "go mod get" "go mod remove" "go mod update path@specific_version" "go mod downgrade path@specific_version" and so on? It makes everything stick to "go mod" instead of two type of command.

Wasn't this published earlier ? 🧐

millitary standard mike

You can just use apt instead of apt-get when you run it from the prompt. It's shorter and it's a single command for multiple actions. The apt-get, apt-cache, etc are still to be used when scripting for clarity.

7.40 is the part you should jump to if you want to directly learn to code around Go Modules and skip the Modules and SemVer theory part.

Semantic versioning has been fundamentally broken since its inception.

Repossery? Are you trying to say "repository"?

What is a reposiry? Is it similar to a "repo"? I think you forgot and transposed a couple of letters there.. reposiry repository hm.. levenshtein difference of 2... compiler-brain says: DOES NOT COMPUTE reposi__ry repository you need to enunciate those two sounds.... tee, ooo do you see how what you are saying is different from the dictionary defenition? re-po-si-to-ry re-po-si-ry So no, I was wrong, you didn't transpose anything, you just skipped two letters. Maybe not a big deal, but it is surely funny :) I am going to test this out on my co-workers. REPOSIRY! or even RESORY or even RESY. I am sure they are smart dudes and will understand what a RESY is ;)