Hacker News Reader

The debuggers integrated into web browsers are actually really good, about the same level as most IDE-integrated debuggers.

Ironically the JS debugger is the only one I ever use because it's the only one that "just works".

when you write async JS code the debugger essentially adds no value over printing

Not in my experience, async JS/TS code is perfectly fine debuggable (at least with setting a breakpoint here and there).

the callstacks are hard to read and watching variables across context boundaries is difficult. yea you can pause the program with the debugger, but doing so doesn't give much of a picture of how the program is functioning. I've found seeing the prints from all the 'threads' gives a better sense of what's happening