[kevingadd]

> Stack frames go away the second you release control back to the event loop which is by far the more pernicious problem.

Sadly the opposite is true today: If you're doing async/await programming in Chrome (and Firefox too, I think?) the runtime actually tries to carry your stack across event loop turns and this will be visible in Error.stack. This happens even with the debugger closed in my experience (the massive stacks are really annoying)

[silon42]

There are times where they are very useful.

[iggldiggl]

Having had to debug issues in unfamiliar async-using code without the benefit of that feature (Now who the hell originally called this function?), I'd tend to agree.