12 ms·
He is just in love with the shiny toy: Go is good, Go doesnt have and IDE => IDE is bad. I have seen a guy on HN saying that debuggers are bad and logging debu
by CmonDev 11y ago
He is just in love with the shiny toy: Go is good, Go doesnt have and IDE => IDE is bad.
I have seen a guy on HN saying that debuggers are bad and logging debug messages is superior :). Future is here, but it is sooo unevenly distributed.
- hacker_9 11y agoThat's another good point - no official go debugger. Additionally IDE's give you breakpoints, line highlighting, contextual variable inspection and so on.
- sagichmal 11y agoFor certain classes of software development, specifically distributed systems, debuggers are bad (or, at least, effectively useless) and logging debug messages is superior (because it's the best way to rebuild a chain of causality). It's all about context. Go is a great tool for certain things. Understand the boundaries of those domains, rather than castigating the tool.