4 ms·
I'd note that's only an issue if you don't have a good IDE. In IntelliJ you can breakpoint on an expression that uses chaining, hold down the alt key and then
by mike_hearn 8y ago
I'd note that's only an issue if you don't have a good IDE.
In IntelliJ you can breakpoint on an expression that uses chaining, hold down the alt key and then click on the expression you want to evaluate. It turns into a hyperlink and can be viewed easily.
- kcmp 8y agoI think needing a heavy IDE to comfortably work in a language/paradigm is a negative
- mike_hearn 8y agoYou don't need an IDE but it solves problems like "I don't want to chain my methods because my weak debugger can't handle it well".
- sagichmal 8y agoChained method calls being difficult to debug does not necessarily mean using a debugger. It can mean difficult to insert clarifying code in the middle of the chain: print statements, or additional value checks, and so on.
- bmurphy1976 8y agoChained methods also don't diff as clearly (the one liners anyway).
- pjmlp 8y agoThey do on GUI diff tools by using different colors.
- Cthulhu_ 8y agoIt's still not as clear as just splitting across lines, plus in most tools you need to explicitly indicate you want to highlight word diffs. But more abstractly speaking: are chained calls, from the POV of a human that didn't write it, or wrote it two months ago, more readable than a number of statements on multiple lines?
- pjmlp 8y agoGiven what Lisp, Smalltalk, Mesa/Cedar, Oberon, Delphi, VB introduced as productivity tooling, I see as negative programming as if my computer was still stuck in 80x25 green phosphor terminal.
- scroot 8y agoAmen
- simias 8y agoThat's a silly caricature. I could retort "I see as a negative if my development environment takes 40GB of RAM and half an hour to boot up" and it would be on the same level. Debuggers are great but they're not always practical, for instance for debugging remote targets with limited connectivity. Actually in some situations you may end up having to buy expensive licenses for closed source software to run a debugger on certain hardware (although that might not be a concern for Go). I'm also of the opinion that firing the debugger as soon as something unexpected happens instead of taking 10 seconds to reason about your code might lead you to miss a more general problem with your architecture as you focus solely on the symptoms, but that's of course a lot more subjective and your experience may vary. Personally I generally tend to use debuggers as a last recourse when I really can't make sense of what's going on through "static" analysis.
- marcus_holmes 8y agoalso, if you write a ton of log statements because that's how you debug, then when your production system blows up and you can't fire up the debugger, you have something to work on.
- marcus_holmes 8y agoGenerally speaking, Gophers don't interactively debug. There is some support for it, but it's historically been difficult and we have tended to adjust to logging everything and working out the problem from the logs.
- lucio 8y agoThat's OK but when using "logs" it takes more time and tries to find a complex bug than to search for it using an interactive debug tool.