But there are dozens of other misfeatures in... Basically applies to most mature widely used languages that have evolved by adding features. In many software p

But there are dozens of other misfeatures in... Basically applies to most mature widely used languages that have evolved by adding features. In many software projects, the bias is on the side of adding too many features and not accounting for the costs, to the point where someone feels a bit of pain and complains. In Go, the bias is in not having enough, to the point where someone feels a bit of pain and complains. I'd bet that more language designers are going to opt for the 2nd strategy as we go forward in the 21st century.