* the author (and everyone else who complains about Go) simply hasn't made any appreciable investment in learning Go
* the language itself doesn't naturally lend itself to most programmers easily finding the most succinct/powerful expressions available, instead providing a grain that favors clarity over other values
* the documentation and tutorials available don't teach programmers how to write succinct and expressive Go