Follow
Since I'm often asked why I like Go so much, I've fleshed out my thoughts on the subject pretty thoroughly through many iterations. I haven't thought nearly as often about what I *don't* like about Go, beyond the very rare cases (for me) where generics would be nice to have, and a few minor inconveniences here and there.
To my fellow Gophers: what are your biggest Go gripes? Not e.g. specific use cases where it lacks popular libraries, but persistent annoyances
@cn All that said, if I'm writing a service, I'm reaching for Go more often than not. I moved to OCaml over the last two years for PL R&D and day to day Swiss Army knife stuff, which has been rewarding, but I've found it inferior to Go for a range of different tasks.
@cn speaking as user since 1.0:
- core team is increasingly high-handed and dismissive (most of the other issues stem from this)
- grafting RubyGems on top of the package system was a bad idea
- there is a dangerous crop of unfixed compiler bugs nobody plans on fixing
- the idiomatic way to do things like variants is incredibly kludgy
- channels are a huge footgun for new people and the tooling around them is still primitive