alt Hacker NewsJust to add my two cents—I’ve been writing Go professionally for about 10 years, and neither I nor any of my colleagues have had real issues with how Go handles errors.
Newcomers often push back on this aspect of the language (among other things), but in my experience, that usually fades as they get more familiar with Go’s philosophy and design choices.
As for the Go team’s decision process, I think it’s a good thing that the lack of consensus over a long period and many attempts can prompt them to formally define a position.
Replies
This, it’s always the new people complaining about error handling.
I have many things to complain about for other languages that I’m sure are top-tier complaints too
I have a similar level of experience with Go, and I would go so far as to say it is in fact one of the best features of the language.
I wouldn’t be surprised that when the pro-exception-handling crowd eventually wins, it will lead to hard forks and severe fragmentation of the entire ecosystem.
That's just survivorship bias isn't it? The newcomers who find Go's design and/or leadership obnoxious get a job that doesn't involve doing something that they dislike.
Yeah once you've been using it long enough for the Stockholm syndrome to set in, you come to terms with the hostile parts of the language.