I use printf-debugging the vast majority of the time. But that's fine if you know you have an alternative and you're just lazy to use it.
Recently I was working on an embedded platform which had no debugger support at all. There was some On-Chip debugger option, but it required some soldering and hacking some jtag cable, still too lazy.
Go at least has stack traces with no extra tooling, which is a big deal.
Anyway, the more tools the better; you're gonna miss them when you need them most.