[quelsolaar]

To me the debugger is perhaps the most important tool and I much rather have a bad editor with a good debugger than a great editor without. I find that typing code is never the limiting factor in productivity, being able to understand what your code does is, and a good debugger is a game changer. The same goes for languages, there is a lot of discussion about what various languages do, but not what debuggers are available for them. Visual studio has many faults, but IMO it runs circles around the competition when it comes to te debugger.

[whatever1]

Debugging is the one reason I tolerate interpreted languages.

The fact that you can pause execution and start writing commands to execute on the fly in the debug console is VERY POWERFUL.

[quelsolaar]

As a C developer, I REALY want a interpreted C compiler with a crazy good debugger for this reason. On average I think C has really good debuggers (its a simple language that has been around for a long time) but there is so much more one could do. A few years ago i wrote a prototype called OPA, with some cool potential features. https://www.youtube.com/watch?v=pvkn9Xz-xks

[cxr]

"Interpreted C?" (2019) <https://www.tuhs.org/pipermail/tuhs/2019-May/017790.html>

"The ups Debugger" <https://ups.sourceforge.net/>

[lispm]

...and you don't need even 'interpreted languages' for that...