I'm not sure how you "abuse" debugging-- can you elaborate on that? The debugger runs in as many threads as the app itself. If you're debugging C#, and your pr

I'm not sure how you "abuse" debugging-- can you elaborate on that? The debugger runs in as many threads as the app itself. If you're debugging C#, and your program is in 37 threads, you can debug all of them simultaneously or debug one and ignore the others. Understanding the code and keeping it in memory sounds like a great practice, but it also seems entirely orthogonal to using a debugger. I have the exact opposite attitude: I live in the debugger. Most of my resistance to trying "new hot" languages is their universally terrible debuggers. (Usually they either don't exist at all, or only exist in CLI form.) IMO, if you don't have a working, stable, graphical debugger, your programming language has no business being 1.x.