worth noting the article was published near the end of July 2016 and these methods were only added in the following month (and packaged as part of a Go release in October). i'd argue that since it's a retrospective of a few years of use, it would be fair to include that criticism even if that release had come shortly before publication
The criticism is fair given the timeframe, but it equally useful to point out for the readers coming here today how the language has evolved since that time.
https://play.golang.org/p/JNhlfYoZgCV