why are they against it though? nobody is stopping you from writing if err != nil?
-
-
-
A lAnGuAgE sHoUlD hAvE oNlY oNe WaY tO dO tHiNgS. No idea why they have multiplication, when repeated addition was RIGHT THERE ALL ALONG.
- 4 more replies
New conversation -
-
-
The people that really really like go think that every feature is the essence of simplicity itself, and written by god himself.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
We have seen people not accepting s change like this before: think about Java Optional or functional interfaces. There are still a lot of people against it. Go devs are among the most stubborn people I have ever seen. They are *sure* they are right. They won't change idea.
-
's/Go devs/Go designers/g'
End of conversation
New conversation -
-
-
Rust is a far more pleasurable language to work with, when compared to Go
-
APL end ALGOL are far more sensible languages to work with, by that standard. That doesn’t mean I expect to touch them ever again in my career.

End of conversation
New conversation -
-
-
Are you saying that try is great and that opponents' worries are overblown, or that it shouldn't be done, but if it is, the people with the right of it will be overwhelmed by others who love the feature?
-
I think the former. I remember lots of doubt around the try macro and ? operator. Now it seems so obvious to most I don't hear anyone complaining about it anymore. The error handling patterns in go are so common, I had previous coworkers use shortcuts to auto generate the code.
End of conversation
New conversation -
-
-
Rust, Go, and Swift are designed to be real languages (no VM), but still safe and performant, so for performance some "cool" features are sacrificed "or at least discouraged" (like GC in Rust,try in Go and Swift, full OOP support (like Java/C++) in Rust and Go, overloading in Go)
-
'try' has nothing to do with performance and is just to reduce repetition and increase code readability
- 3 more replies
New conversation -
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.