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?
[ Parent
| on HN ]
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 =)
> 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
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/