What I'm going to say won't make much sense at first, but I find I don't really need a debugger when writing Go. A log statement here and there combined with un

What I'm going to say won't make much sense at first, but I find I don't really need a debugger when writing Go. A log statement here and there combined with unit tests and the race detector get me through every time. I absolutely refuse to touch Java/C#/C++ without a debugger, but that's because they're a lot more "magical" - lots of layers, lots of magic, 'heavy' types. Go is a lot more explicit about what's going. It is more verbose, yes, but you also know how things work by just looking at them. I'd love a debugger for Go, sure, but I just don't need one.