I don't get the mentality of people who don't feel the importance and satisfaction of being able to step through their code line-by-line and see everything coming to life in a debugger window, even if its for sake of watching it, not for finding a code bug. Some people seem to never have used one for years and they take it as a sign of weakness if someone says they need one to find a bug rather than looking at the code.
I haven't and if its up to me, I would never use Go again, just because of the piss poor debugging experience in a language that's so new. Google engineer's mentality is very old school and anyone who enjoyed the beauty of conditional breakpoints and step-through debugging in modern IDEs will know exactly what I am talking about. Go is so new yet built with incredibly ancient mentality.
Not even game consoles are as bad.
Nowadays it has gotten much better versus the Android 2.1 days, and after 10 years it still isn't where Apple, Microsoft, Sony, Nintendo platforms are today.
There’s a time and place for proper debuggers and (more?) time and place for a simple print statement in my humble opinion.
My initial impressions of delve was "Oh it's basically GDB for Go". But seems like the debugger has become more stable and more mature over the years by shipping language specific commands; like `goroutines`.
GDB still has a lot of value if you're working with a non-amd64 architecture or want to dive into cgo parts of a codebase, but Delve is a great addition to your toolbelt!
I'd urge you to give it a spin next time you come across a weird bug ^^
Like... a REPL?
Kinda like the console in web developer tools (F12)