Hacker News Reader

A debugger that cannot be attached to a living process, that cannot change or execute data dynamically, is not a debugger. Unfortunately, many languages provide "debuggers" that fall into that category.

View on HN

Well I guess the Go community is a little bit too passionate about any update regarding Go, even if the introduced new thing is subpar compare to other languages, like this one in the post.

I think that the main issue is that debuggers are often dismissed in terms of importance, and many don't see the true value of debugging beyond simple step-by-step execution.

This is not unique to Go: python's several debuggers require cooperation with the inspected process. This is exactly the opposite of a buggy situation. gdb's python support is very limited in terms of debugging capabilities, yet it's the only option you have if you're using an external event loop handler, such as gtk/qt/glib (not so uncommon). I guess I should be grateful I have those at least.

I absolutely agree with you, my problem is that if I bring these things up in an discussion about languages it results in "who are you kidding, we don't need that feature!" sort of comments. Personally I find it hard to do any sort of computation without the ability is inspect what is going inside.

Reply on news.ycombinator.com