>In Go, with proper error handling Well yeah, if you handle errors properly, you get better results than if you don't. The point is that with exceptions, it f

>In Go, with proper error handling Well yeah, if you handle errors properly, you get better results than if you don't. The point is that with exceptions, it fails loudly and you get the cryptic message even if you forget, whereas with Go, if you forget to handle an error, you just get weird behaviour and corrupt data. And if you want more helpful error messages, you can catch the exceptions and report the context just as easily as you can in Go.