Is there anyone out there who is actually familiar with a debugger for the tool they're using and still prefer print debugging?
No?
That settles that then...
I for one use both print debugging and actual debuggers (I've used the C# VS debugger, windbg, Java debugging in Eclipse, NetBeans, and IntelliJ, CLI gdb and pdb, Emacs GUD for gdb, pdb and Go delve, Emacs edb and the CCL debugger from SLIME). Sometimes it's awesome to point a debugger at a core dump and fix a year-old memory leak, or just see windbg point out a deadlock involving 5 locks in 2 different processes. Other times it's awesome to interpret debug logs and figure out a how a flow in a customer setup got interleaved and produced a race condition two weeks ago, which is causing a crash today.
Of course a debugger can't replace the need for logs entirely!
The article is in fact claiming that a debugger can replace print debugging entirely, that's why I read your comment in this same vein.