3 ms·

I find this goes against the go simplicity. I continually find that Maven & Gradle are much easier to use than Go's package management system for versioned depe

I find this goes against the go simplicity. I continually find that Maven & Gradle are much easier to use than Go's package management system for versioned dependencies.

Thaxll 5y ago
When people release 500+ pages book to explain a build system, you know you're in trouble. https://www.amazon.com/Maven-Definitive-Guide-Sonatype-Company/dp/0596517335/ https://www.amazon.com/Maven-Definitive-Guide-Sonatype-Compa... Go is way way easier to use than Maven and Gradle. I think I use only 4 commands daily to manage dependencies in Go, it's that easy: https://github.com/golang/go/wiki/Modules#daily-workflow https://github.com/golang/go/wiki/Modules#daily-workflow
- ______-_-______ 5y ago
  This might be the first time I've heard someone say comprehensive documentation is a bad thing. Go's module docs are 82 printed pages. Is that better or worse? https://go.dev/ref/mod https://go.dev/ref/mod
  - Thaxll 5y ago
    Every place I worked, Java build pipeline has always been cumbersome, it's one thing that one guy knows and you're afraid to change it because it's complicated.
  - jrockway 5y ago
    That's 36 pages printed (try printing it), and includes the grammar for the go.mod file, information about the ecosystem of services available (module proxy, sumdb) and their protocol definitions, how to access and publish private modules, etc. It doesn't skimp on thoroughness anywhere.
  - layer8 5y ago
    The Sonatype Maven book isn’t actually that comprehensive, unfortunately.