>From my experience/point of view, GOPATH is the first concept you have to >understand for managing correctly your project. Even if this concept is finally simple. IMHO, this is the first strange/bad feeling with Go. And lot of my workmates prefer to not start a new project alone (even if the language is simple) because they aren't feel good enough with this actually simple GOPATH concept (and all that derive from it, mix /vendor and own source). Specially, when the dev team comes from technology base on directory project (as Java/maven). Surely, GOPATH spirit fits well for some enterprises (with big monorepo).
That why we use gb, even it is not official way to manage project and with some lack of features (no lock file, no semantics version into your vendor manifest... ) That is my 2 cents. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
