3 ms·
> error handling is three times the code line volume versus the core business logic. That's not ok It is ok. That's really how it should be IMO. The "problem"
by IshKebab 4y ago
> error handling is three times the code line volume versus the core business logic. That's not ok
It is ok. That's really how it should be IMO. The "problem" is that Go doesn't allow you to say "eh, we'll just give a stack trace to the user, and then they can delete it print Oops something went wrong" which is apparently what most people want from their error handling.