> Since TS has stack traces That's the key here - I would not need anything like this in Python either, because it has stack traces. But Go designers decided

> Since TS has stack traces That's the key here - I would not need anything like this in Python either, because it has stack traces. But Go designers decided to really drop the ball here - there are no stack traces on "err" values, so one has to implement them by hand as article demonstrates. Which is a pity. Go has a lot of great things going for it, but the error handling just makes everything unnecessary verbose.