5 ms·
Go still has a few annoyances: error handling and casting things to/from interface{} are the most painful of them. Certainly, it's still ways better than C. Bu
by nine_k 6y ago
Go still has a few annoyances: error handling and casting things to/from interface{} are the most painful of them.
Certainly, it's still ways better than C. But the resulting boilerplate and copy-paste programming ought to be a source of errors.
(I'm happy to see the generics proposal coming closer and closer to a future feature.)
- nprateem 6y agoError handling is such a train wreck. Manually returning an error in 2021? What were they smoking?
- it 6y agoIt's actually really nice to have the good quality error messages that Go encourages when something goes wrong.
- nprateem 6y agoIf you remember to write them and propagate them...
- jamiesonbecker 6y agoExplicit is better than implicit, and you can't get much more explicit than that.
- erik_seaberg 6y agoNobody wants to write or read PUSH EBP MOV EBP, ESP SUB ESP, 12 a thousand times a day. The best you can do is avoid screwing it up. So when you write a function in any language since 1960 it just happens. Stopping a function halfway and bubbling an error up the stack should also just happen.
- _peeley 6y agoI agree, although there are IMO more optimal and explicit ways to handle errors - Rust and Haskell come to mind. When dealing with a Result/Either/Maybe or some other functor, you have to acknowledge the context of the value, i.e. that the value could possibly be an error. This way the error handling is baked into the type system in a way that's hard to replicate in languages that just return error codes or exceptions.
- antonvs 6y ago> Explicit is better than implicit Which just demonstrates why slogans are not a good substitute for thought. They're good for programming a community though.
- nprateem 6y agoIf you believe that I hope you only write in assembler
- Animats 6y agoError handling is not that great in either Go or Rust. It wasn't that great in Python, either, until Python standardized its exception hierarchy. That seems to be the key - get everything to use the same exception format, especially the libraries. How the error values are passed around is less important.
- lenkite 6y ago1 always need to spend 30 mins educating everyone on the "nil interface" on Go. Go lang is fine for small network services that do just one job but it doesn't scale up as an app programming language for large teams. It has far too many edge cases and gotchas. Also, loads and loads of boilerplate - making Java look elegant.