> if debuggers took less time to start than a full "add print -> recompile -> relaunch app" cycle as is my experience with C++, they would certainly get more us

> if debuggers took less time to start than a full "add print -> recompile -> relaunch app" cycle as is my experience with C++, they would certainly get more use. This is a really good point - programmers seem to prefer making "dead"/batch-processing programs over "living", interactive, persistent systems (according to Steve Yegge's definition of those[1]). This style, in addition to being very Unix-y, also lends itself really well to printf debugging - you just add printfs, recompile, and re-run. I build "live" programs, and make heavy use of the debugger - although that might be because of tight integration of my debugger with the rest of my tools - although that might be because other users of this language tend to prefer the live style and build their tools to adapt. [1] http://steve-yegge.blogspot.com/2007/01/pinocchio-problem.html http://steve-yegge.blogspot.com/2007/01/pinocchio-problem.ht...