Go's Tooling Is an Undervalued Technology
I definitely appreciate many parts of go&#x27;s tooling ecosystem: pprof, gofmt, go get (in GOPATH mode), and go bug are all pretty good ideas. pprof in particular and the various profiling tools build out around it are great.<p>That being said, I haven&#x27;t found all aspects to be as nice - most notably among these is the lack of a good debugging environment. There is no debugger in the go tool, and users rely on delve[0] for their debugging needs. The dlv command line tool has actually gotten a lot better over the last couple years (props to the maintainers!), but integration in to visual front-ends is still lacking. VS Code and GoLand integrations at least are lacking to the point of it being nearly unusable except in the simplest cases. For a few examples, stepping is painfully slow (there are several machines&#x2F;OSes I use), conditional breakpoints don&#x27;t seem to work, keeping the tools up to date doesn&#x27;t work consistently which means updating the underlying go&#x2F;delve tooling or the IDE will frequently break the experience, and defining your debugging processes (e.g. via VS Code&#x27;s launch.json) is tedious. None of these are go&#x27;s fault per se, but it diminishes the overall experience.<p>In general, it would be nice to have a better debugging experience, esp. since I prefer a GUI tool to the command line for debugging. In the meantime, I might switch back to just using command line dlv.<p>But regardless, definitely agreed that go&#x27;s tooling on the whole is great. pprof has saved my skin on countless occassions!<p>[0] <a href="https:&#x2F;&#x2F;github.com&#x2F;go-delve&#x2F;delve" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;go-delve&#x2F;delve</a>