What’s wrong with Go’s error handling?
Peter Goetz

I specifically like your point on stack traces. When debugging and maintaining larger systems where you don’t know all components internals good stack traces can save you a lot time and energy.

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.