[jesse__]

I came here to write exactly this .. if I was drinking something I would have spit it everywhere laughing when I read it.

I guess 'many developers' here probably refers to web developers who don't use the debugger, cause it's mostly useless/perpetually broken in JS land ..? I rely heavily on the debugger; can't imagine how people work without one.

[flohofwoe]

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

[eddd-ddde]

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

[bippihippi1]

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

[flohofwoe]

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

[bippihippi1]

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