You're exactly the problem the commenter is talking about. I got used to it within a month and while I would appreciate better error handling (if that even exists), I don't think the solution should be rushed and I don't think the way Java handles it is right.
Re:Go proposal: Leave “if err != nil” alone?
by crimsonalucard on Friday June 28, 2019 @01:38PM
(#20306831)
I agree, but leaving it because people are used to it is not the right solution imo.
It's still a big issue overall.