If it were true, it would be because nobody who wants exceptions uses Go. The use of the language is self-selected based on the match between preferences and available features, so then the preferences aren't surprising.
But in fact, there probably exists a minority of developers who somehow had Go foisted upon them, and who would would like it to have basic features like exceptions.
I like go for the most part, but the error handling drives me bonkers. I'm a big exceptions/errors with try/catch/finally statements person. They do a MUCH better job of forcing you to handle exceptions/errors than return values. I'm sure this will start some argument of why returning an error value is better. I've spent the last 35 years programming in a large number of languages and my _personal_ opinion is that try/catch trumps returning error results.
But in fact, there probably exists a minority of developers who somehow had Go foisted upon them, and who would would like it to have basic features like exceptions.