News for hackers. Stuff that matters.
Re:Go 1.17 Release Notes by systemvoltage on Tuesday August 17, 2021 @01:06AM (#28206408)
Not a GO dev, has the debugging experience improved?
Re:Go 1.17 Release Notes by theshrike79 on Tuesday August 17, 2021 @01:28AM (#28206503)
Dunno, 20 years in the business and I still debug with print statements.

It's enough in 95% of cases and it works every time in every environment. In the time it takes me to get a debugger running and attached to a process, I've print-debugged it and fixed it already =)

Re:Go 1.17 Release Notes by maccard on Tuesday August 17, 2021 @06:16AM (#28208182)
> In the time it takes me to get a debugger running and attached to a process,

In any modern editor or IDE, getting a debugger running and attached to a process usually amounts to opening a folder, adding a breakpoint and pressing F5

Re:Go 1.17 Release Notes by ithkuil on Tuesday August 17, 2021 @04:30AM (#28207514)
Same here. I very rarely reach for a debugger. Especially with Go where you can recompile the binary very quickly.

I tend to reach for a debugger when doing post mortem debugging or when I work with C where that's usually the easiest way to get a stack trace when a program crashes.

That said, time travel / reverse debuggers can be quite useful indeed: see http://choly.ca/post/debugging-go-with-rr/

Re:Go 1.17 Release Notes by harikb on Tuesday August 17, 2021 @02:55AM (#28206959)
VsCode or IntelliJ with delv works beautifully for most common tasks. But don’t compare to JVM/Java. It does get trickier if you have many concurrent/goroutines but that is not unique to Go.