The Chaotic History of Package Management in Go (so far) 

📝Get your *FREE Golang Cheat Sheet* - golangdojo.com/cheatsheet

Thanks a lot for sharing the most valuable and most required information in golang

Before the introduction of Go module, I've seen Go package management is chaotic, with no way (at least I didn't know) how to lock dependencies. Go team seems a bit late to realize that as soon the ecosystem grows a sophisticated package manager is a must, but better late than never.

Thanks for the vid, it is really helpful as I'm starting to learn Go and documentation about package managment was confusing to me with all the info about previous approaches.

Go package manger is the only reason why I use rust

thank u ser i need this video so bad

Why is ..hello world program on go is slow in my office windows machine and antivirus runs when i start executing...go run

Go mod has given me MORE headaches than anything else in Go and I've been doing Go since 2011. If you could go more in depth that would be fantastic

Answer to your first question Yes I have always been confused with package management

Who is the second dude that explained the topic and why? Did I miss something?

bro i miss yooooo

Hey Wallace can we get a video on Go's Garbage collection.

Anyone who remember GLIDE, we were using

i didnt know about go workspaces!

JavaScript also has a goofy history with modules.

i still dont like the package management from go

Go shouls have better dependency management. 1. Can go pull the depencies if we change the go mod file instead of go commands? 2. Go should find better way to deal with depencies may be like maven/gradle.

"go work" - facepalm

Go is bad designed language