4 ms·

The only bad design I see is the missing generics. The path, modules, and error handlings are features to me, not drawbacks.

• papito 7y ago
  The Go path is going away. This is being replaced by modules (the feature that I actually like a lot, especially the vendoring). The problem is, why did it take almost a decade for a modern language, at Google nonetheless, to get a proper dependency management feature? To me it says that the Go vetting process at Google is seriously constipated, perhaps because people there just say "this does not look right, but who am I to question the decisions of Rob Pike and Ken Thompson?". And then we end up with these language design decisions from the 1970s. And also, amazingly, error management in Go may have actually been made worse in 1.13: https://www.reddit.com/r/golang/comments/biexq0/go_113_xerrors https://www.reddit.com/r/golang/comments/biexq0/go_113_xerro...
  • apta 7y ago
    > perhaps because people there just say "this does not look right, but who am I to question the decisions of Rob Pike and Ken Thompson?". And then we end up with these language design decisions from the 1970s. Yep. golang is one big appeal to authority fallacy at work.
  • erik_seaberg 7y ago
    Google develops everything at #head of a monorepo, so their dependency management problems consist of “please rollback ASAP, your changelist broke the world”.