This reads like script kiddies who became professional programmers and just want things done how they've always been done.
Error handling in go is not concise, and calling it explicit is in insult to anyone with a modicum of abstract reasoning skills. Error handling in go is not explicit, it's verbose. Error handling in go is not concise, it's broad. Error handling in Go is not consistent, it's an exercise left up to diligent programmers.
As golang's code base grows, you're going to see this mistake play out over and over and over again.
Having a Result<T> construct would have been great for go.
Error handling in go is not concise, and calling it explicit is in insult to anyone with a modicum of abstract reasoning skills. Error handling in go is not explicit, it's verbose. Error handling in go is not concise, it's broad. Error handling in Go is not consistent, it's an exercise left up to diligent programmers.
As golang's code base grows, you're going to see this mistake play out over and over and over again.
Having a Result<T> construct would have been great for go.