> Until you get used to the debugger, you will ask yourself this question.
As a counterpoint to this, I was pretty much exclusively a debugger guy for the first 10-12 years of my career. Now I'm pretty much exclusively a logging kind of guy. Familiarity with a debugger has nothing to do with it.
> Console logging is bad for recursive functions, loops, huge variables, etc.
And debuggers are bad for focus/blur event handlers in UI code because they change the focus state of the thing you're trying to debug.
Ultimately, neither of them is perfect, not all problems are alike, one is not an objectively better tool than the other. They both have merits.
I think the print/logging tactic get a little bit of a bad-reputation mainly because of the minority out there who do it because it's the only approach they know how to take.
As a counterpoint to this, I was pretty much exclusively a debugger guy for the first 10-12 years of my career. Now I'm pretty much exclusively a logging kind of guy. Familiarity with a debugger has nothing to do with it.
> Console logging is bad for recursive functions, loops, huge variables, etc.
And debuggers are bad for focus/blur event handlers in UI code because they change the focus state of the thing you're trying to debug.
Ultimately, neither of them is perfect, not all problems are alike, one is not an objectively better tool than the other. They both have merits.