There's nothing "antiquated" about Go's error handling. It expresses a position that you might not agree with -- that errors are no less important than happy pa

There's nothing "antiquated" about Go's error handling. It expresses a position that you might not agree with -- that errors are no less important than happy path code -- but that's not right or wrong, it's just a position.