> Like: The package and build system is amazing and just works. I don't have much experience with go, but that's not at all my experience. I had the compiler p

> Like: The package and build system is amazing and just works. I don't have much experience with go, but that's not at all my experience. I had the compiler panic on me for daring to run "go get", as described here: https://github.com/golang/go/issues/47979 https://github.com/golang/go/issues/47979 This issue has now been closed, but there are several others open with the same symptoms. The response by a golang maintainer was: > It seems likely that there is still a bug here, but the code is complex enough that we're unlikely to find it by just reading through the code. Anecdotally, i've tried to fork the imported module to remove some dependencies i was not using, and failed miserably, as explained here: https://github.com/ooni/probe-cli/pull/986#issuecomment-1327446013 https://github.com/ooni/probe-cli/pull/986#issuecomment-1327... I have experience with C/Rust import systems and i can say with 100% confidence that golang's module system is far from amazing.