He has refused to allow for configuration of TLS 1.3 ciphers in Go: https://github.com/golang/go/issues/29349
Thanks to this decision: if a particular cipher is found to be weak or vulnerable, people using Go won't be able to immediately disable it. Instead, they'll be forced to wait for a release or patch, and possibly have to backport it to the version they're running in production.
Another scenario, as pointed out in that ticket: sometimes other vendors don't properly implement ciphers on their end, and there's an incompatibility. Prior to TLS 1.3, one could just disable that particular cipher, perhaps even just for a particular connecting client.
His response was, paraphrasing: "TLS 1.3 is amazing and awesome and will not have the same problems prior TLS versions had. It needs to Just Work, if there's a security issue we'll issue a patch, and if you can't apply it in a timely fashion you're incompetent." He seems unaware that not everyone uses Google's "just roll it out to a few hundred nodes and keep an eye on them" approach to SRE, or that major organizations don't have time to wait for a patch - they need a quick switch flip until the patch is out and can pass their normal validation before moving to production.