It seems like golang designers are totally isolated from what's been happening in the last 30 years in languages design. They still insist on their weird way of error handling just like they were stubborn for years and years on the lack of package management and eventually a very weird and rudimentary way of it. It's sad because I use this language extensively but its weirdly mediocre design is totally unfathomable. It's like they are very stubborn to do anything but the right thing.
> I use this language extensively but its weirdly mediocre design is totally unfathomable.
So then why do you use it extensively?
because I use it in my day job, not by choice.
So what language do you think does everything the right way?
That's a stawman fallacy. There is no perfect language. However, there are languages that almost are strictly superior to others. Java and C# in this case are almost strictly superior to golang in almost every front.
Well, unless you consider Go's concurrency model superior, as well as the fact that you get native binaries.
I wouldn't necessarily call Go's concurrency model superior, it seem like that initially but after all hype died out a bit it has issues. It essentially just offers one way to do concurrency. That might fit really well for some problems, not so much for others.
I don't know what to say about native binaries, when a Go's "hello world" app is as big as an entire os[1].
Perhaps I'll upset some, but IMO Go would be another obscure language that no one cared about if it didn't come from Google.
> but IMO Go would be another obscure language that no one cared about if it didn't come from Google.
The people who worked on golang also worked on another similar language called limbo before they were at google. You can guess where that one ended up.
The people who worked on Java also worked on Dart after joining Google. You can guess where it ended up.