delve

The Go debugging integration with Visual Studio Code is built on top of the Delve debugger, but exposed through the integrated debugging UX of VS Code. We're working with the Delve developers on a few things to help make this experience great - including Windows support (https://github.com/derekparker/delve/pull/276).

I would choose Go. It comes with an excellent built-in package net/http (https://godoc.org/net/http) that quickly allows you to setup a web service. An Go's mechanic (?) of implicit satisfaction of interfaces allows you to do some really cool things. One of the gripes about Go seems to be error handling, and your code ends up with a whole bunch of 'if err != nil { stuff }'. Matt Silverlock (http://elithrar.github.io/article/http-handler-error-handlin...) talks a bit about how you can use some of Go's strengths to create a web services without any frameworks or packages that aren't built-in. Go and net/http is very powerful and allows you to do very much without needing any external packages. If it was up to me, I would write the service in Go and run it in a container somewhere. But the container is not required :) Go has been a bit lacki

Not that there's anything wrong with using a debugger as a tool, but I find it hard to understand why it's such a stringent requirement for some. I've never really had the need for one outside of a few instances over many languages, and I know many others that feel the same, which covers a much greater range of languages and styles of programming. Even so, I'm eagerly awaiting a good Go debugger when one arrives. There are some being worked on, like delve (https://github.com/derekparker/delve/), which might be the most ambitious, but it's only recently becoming usable. The problem is partly due to my first statement, there's not a huge demand for these in the language ecosystem, so development has been slow.

https://golang.org/doc/gdb https://github.com/derekparker/delve

I wonder if the author had tried using Delve (https://github.com/derekparker/delve) to see if that is any better/more featured for the problems he was having.

It's largely accepted that while you can use gdb, it's not really good at debugging go code. from your own link.. "GDB does not understand Go programs well" https://github.com/derekparker/delve delve as mentioned other places is more of a true go debugger

That's no debugger. That's a debugger: https://github.com/derekparker/delve If you want to attach to running processes, use delve, it's awesome. For me personally, even with Go's short build times, you can't just deploy a new binary into a running system to see where a problem lies. Sometimes there is just no way around a traditional debugger.

Comparing the Linux and OSX instructions is fun: https://github.com/derekparker/delve#building

Yes: https://github.com/derekparker/delve#breakpoints

There's a more, er... traditional, debugger for Golang in the works: https://github.com/derekparker/delve

https://github.com/derekparker/delve There is a talk scheduled on this at GopherCon 2016. Make sure you have a look at it.

Go on the JVM completely defeats one of the biggest Go selling points for me: compilation to native code. Debuggers are definitely a weak spot, though, I agree. Luckily it's being worked on (https://github.com/derekparker/delve).

> A Debugger https://golang.org/doc/gdb (some limitations IIRC) https://github.com/derekparker/delve (a work in progress, but promising)