It is strange you ask this, cause it was one of my major issues with diving into golang. The reality is that I don't miss it any more, for two reasons. 1. I h

It is strange you ask this, cause it was one of my major issues with diving into golang. The reality is that I don't miss it any more, for two reasons. 1. I have been forced to write solid comprehensive testing. Its a pain, but the pay off has made it worth while. 2. Because you never find all the bugs anyway, instrumentation and logging has become part of everything I do. A framework like go kit can do this out of the box for you or function as a guide for you.