It bothers me when people write a lot of software with hidden jumps in control flow. I want to reason mathematically about the code, not experiment with it to see if it throws these exceptions or retries or what. Is there some layer in the framework du jour that catches them all and spits out an HTTP 200 status html stack trace instead of the expected XML error status?

The objections I personally have against exceptions almost all don't seem to apply for language like Go actually.

The thing that annoys me about exceptions is that they can be slower that you'd think, make safety analysis really hard (i.e. regular control flow isn't too bad, exceptional control flow can be weird), and are a pain to implement. And with Go I don't think of those things as being a priority.