I was excited by Go's approach when I first started using it. But everything about the process of how the language is designed and maintained is, imo, just Bad.
-
-
-
I’ve barely touched it myself but haven’t ever heard bad of it before. What’s your least favorite design decision thus far?
- 3 more replies
New conversation -
-
-
At first I agreed with you, but it'd be a different, not better, language. There's no RAII, so early returns quickly become nontrivial. try encouraged use of defer for annotating errors or involved cleanup, which makes code less linear and harms readability.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Why does try make Go a better language?
-
error handling in Go is currently very explicit and boilerplaty. The Go try proposal was super lightweight. Early return of errors has a good track record of reducing complexity and making code more understandable.
End of conversation
New conversation -
-
-
I listened to a podcast about it recently and was quite surprised at the controversy which mostly centered around explicitness and that “try doesn’t fit all the use cases” when in my mind it’s about ensuring propagation of an error as a pattern but maybe I’m off
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
They are not in the business of building a better language. :-)
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Wow. I find that surprising, the backlash from their perspective must have been massive.
-
More surprising than that is most people seemed to agree with the decision. Judging by HN comments.
End of conversation
New conversation -
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.