The author starts out with a a simple statement: > Many people prefer print debugging over interactive debugging tools. Then explains that eventually develope

The author starts out with a a simple statement: > Many people prefer print debugging over interactive debugging tools. Then explains that eventually developers come around to debugging. He explains all the advantages debuggers have while simultaneously touting his own tools. Then he blames adoption on the lack of engineering effort put into overcoming teething problems and calls for platform vendors to better support debuggers. I feel like the author is living in a vacuum and has no idea how most developers work. Watching his demo for Pernosco makes my eyes bleed. The steps he takes for debugging a crashing Python App are: 1) Reproduce bug and capture with rr 2) Transmit capture to Pernosco 3) Wait Minutes for an Email to arrive. 4) Follow link in Email to Web based Debugger 5) Review Core Call Stack and Assembly for your Python App. If it gets to the point where I need to review core call stacks or assembly to figure out why my code is crashing then I'm probably just going to rewrite it. For most developers writing line of business Apps or scripts to parse data and shove it in a DB, the errors you encounter don't require inspecting CPU registers or walking through assembly. They boil down to a misunderstanding about an object state or contents that's quickly rectified by runtime inspection which is why print statements work so well. By the time the author got to step 4 of his Pernosco demo, most developers using Print Debugging would have fixed their bug and been on to the next one.