Not everything is open source... I get where you are coming from but there's a lot of software out there, that is written in go, that isn't and they want to kee

Not everything is open source... I get where you are coming from but there's a lot of software out there, that is written in go, that isn't and they want to keep it that way as much as possible. go run main.go Using the go debugger in your IDE will blow up when that part of the code that panics on error is hit. Do you still need a stack trace then? You're literally looking at it in your editor. There's a time and a place for stack traces in my view and I enjoy the fact that in Go, it's not on by default. If you're building a cloud service in Go and you're unsure of your branching paths, by all means, use stack traces and eliminate your own errors.