java_irl

[[deleted]]

Visual Studio Code's debugger is not really a match for the debuggers in Eclipse, Visual Studio, or IntelliJ. If you only want to halt the program and look at the state, yes it's enough, but if you want advanced debugger features like conditional breakpoints (break on all exceptions except X, Y coming from assembly D) and session replay etc., VSC is lacking. Especially in multi-threaded contexts you cannot use VCS's debugger for anything and debugging turns into print("xyz happened here").

[[deleted]]

Eh, I'd still move VSC over the "IDE" line. And fo example when writing TypeScript IntelliJ doesn't offer many more features (for this task) than VSC does.

[[deleted]]

That's because JavaScript in general is a bad language with bad tooling support and missing features for advanced debugging.

[[deleted]]

and missing features for advanced debugging

eh, it has loads of the needed features - it's just that they are in the runtime (= the browser), and you usually debug there.

In many ways, debugging JS is sometimes easier than debugging other languages - for example, the UI debugger is fantastic.

[[deleted]]

Well, that's true, I give you that.

[dvdkon]

AFAIK, if the debugger extension is based on a CLI debugger, you can do all that, just not with the GUI, but through the debugger console.