A developer reflects on years of avoiding Go due to GOPATH friction, and how Go 1.11's module system finally resolved that barrier. The post covers what makes Go compelling: simplicity, a great concurrency model, a well-designed standard library, and a consistent type system. It also acknowledges pain points like error handling and the log module, and closes with a plea for the Go team to resist complexity creep in Go 2.0.
Sort: