The problem with go is not it's simplicity, it's it's inconsistency. As a small-minded programmer my hobgoblin is tripping over having to remember that X works this way but not Y, which looks vaguely like x.
It feels like the designers of go tripped over themselves to make things simple for some definition of simple and then ran into some feature they wanted and then just bolted the feature on without thinking about whether simplicity/consistency tradeoffs were a thing.
It feels like the designers of go tripped over themselves to make things simple for some definition of simple and then ran into some feature they wanted and then just bolted the feature on without thinking about whether simplicity/consistency tradeoffs were a thing.