Go modules are not ready yet, after the need of /vendor dissapear then it will be ready.
I know about them, I even read the original longgg VGo articles and I love the idea. Coming from a NPM nightmare projects where errors and random builds occurs is going to be a bless to work with go modules.
I don't know much about Go and modules but I know we use it in my company for a big project. And yes, I noticed that /vendor was committed and my eyes started to bleed ☺️
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Go 1.11 brought the concept of modules that allows to resolve the package management issue, like npm or composer.
I think that Go is production ready for many purposes as it's getting more and more used in software industry (elk beats, docker, openshift...).
Go modules are not ready yet, after the need of /vendor dissapear then it will be ready.
I know about them, I even read the original longgg VGo articles and I love the idea. Coming from a NPM nightmare projects where errors and random builds occurs is going to be a bless to work with go modules.
I don't know much about Go and modules but I know we use it in my company for a big project. And yes, I noticed that /vendor was committed and my eyes started to bleed ☺️