3 ms·
Like: The package and build system is amazing and just works. Simple, yet intuitive and powerful with the introduction of modules. It's hard to quantify the num
by brian_rak 4y ago
Like: The package and build system is amazing and just works. Simple, yet intuitive and powerful with the introduction of modules. It's hard to quantify the number of hours I've saved over other tools hunting down build/linker/dependency management issues.
Dislike: Error handling feels extremely verbose. I like the design choice to return errors explicitly, but it feels like there needs to be a return-if-error syntactic sugar introduced to avoid the endless if err != nil ... return err peppered everywhere.
- closeparen 4y agoHaving worked with Go from the days of vendoring, to Glide, to Dep, it is really amazing to see Go turn its greatest weakness into one of its greatest strengths and most-loved features. It was worth the wait. Here’s hoping the rest of my gripes follow a similar arc.
- ooninoob 4y ago> 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.