Post

Jack
Jack@CaffeineForCode·
@kelseyhightower First Week with Go: "Gezz, this error handling is annoying" First Month with Go: "Ah, no prob, I'll just panic(err)" First Month + 1 day with Go: "That was a terrible idea" First Year with Go: "Go's error handling is BEST THING EVER, how did I ever use anything else"
English
17
55
669
0
zeb
zeb@zebassembly·
@CaffeineForCode @kelseyhightower I'm 10 months 18 days in and I'm still firmly still in the Go's error handling is annoying camp. What happens at the 1 year mark to change that opinion? Explicit error propagation is nice but Zig and Rust have a nicer solution IMO
English
0
0
0
0
MickMake
MickMake@MickMakes·
@CaffeineForCode @kelseyhightower Ya, error handling is nice in Go. I usually extend it a bit more…. Define a type for error and then with a few extra functions on that type, it becomes: if response.IsError() { return }
English
0
0
0
0
Preslav Rachev
Preslav Rachev@preslavrachev·
@CaffeineForCode @matryer @kelseyhightower The moment it first saves your back in production, you start appreciating it ;) I’ve had the exact same mental journey. Now, every time I’m dealing with try-catch in Java, I’m frowning at it.
English
0
0
0
0
arv
arv@arvchz·
@CaffeineForCode @kelseyhightower initially i hated Go's error handling, but after a while i felt that, this is one of the best ways to handle errors in many different situations
English
0
0
0
0
Sam
Sam@3lOr4cle·
@CaffeineForCode @kelseyhightower Especially after you understand modules and now you have that one redundant utils package for every project that makes things easier.
English
0
0
0
0
Paylaş