3 ms·
People give Go's error handing a lot of flak, but I personally love the errors that come out of a quality codebase. Just like your example: single line, to the
by iamcalledrob 6mo ago
People give Go's error handing a lot of flak, but I personally love the errors that come out of a quality codebase.
Just like your example: single line, to the point and loggable. e.g.
writing foo.zip: performing http request (bar.com): tls: handshake: expired certificate (1970-01-01)
Exceptions with stack traces are so much more work for the reader. The effort of distilling what's going on is pushed to me at "runtime". Whereas in Go, this effort happens at compile time. The programmer curates the relevant context.
- gf000 6mo agoWhat? What you write makes zero sense, see my comment here: https://news.ycombinator.com/item?id=47750450 https://news.ycombinator.com/item?id=47750450 And come on, skipping 5 lines and only reading the two relevant entries is not "much work". It's a feature that even when developers eventually lazied out, you can still find the error, meanwhile you are at the mercy of a dev in go (and due to the repeating noisy error handling, many of the issues will fail to be properly handled - auto bubbling up is the correct default, not swallowing)
- iamcalledrob 6mo agoDifferent strokes for different folks. The Go errors that I encounter in quality codebases tend to be very well decorated and contain the info I need. Much better than the wall of text I get from a stack trace 24 levels deep.
- gf000 6mo agoApples to oranges. Quality java code bases also have proper error messages. The difference is that a) you get additional info on how you got to a given point which is an obviously huge win, b) even if it's not a quality code base, which let's be honest, the majority, you still have a good deal of information which may be enough to reconstruct the erroneous code path. Unlike "error", or even worse, swallowing an error case.
- Geezus_42 6mo ago> reconstruct the erroneous code path This is only useful to the developers who should be fixing the bug. Us sysadmins need to know the immediate issue to remediate while the client is breathing down our neck. Collect all the stack traces, heap dumps, whatever you want for later review. Just please stop writing them to the main log where we are just trying to identify the immediate issue and have no idea what all the packages those paths point to do. It just creates more text for us to sift through.
- gf000 6mo agogrep "caused by" Here you are.
- iamcalledrob 6mo agoDon't have to grep my go errors :)
- gf000 6mo agoEspecially when they forget to properly handle an error case among the litany of if err line noise, and you get erroneous code execution with no record of it!
- Geezus_42 6mo agoWhy not just make your errors more readable and not have to use an extra tool?
- gf000 6mo agoWell, just write more readable error messages? How do you make this more readable: ExceptionName: Dev-given message at Class(line number) at Class(line number) caused by AnotherCauseException: Dev-given message at Class(line number) It's only the dev given message that may or may not be of good quality, the exact same way as it is in go. It's a plus that you can't accidentally ignore error cases, and even if a dev was lazy, you still have a pretty good record for where a given error case could originate from.