Protip with this feature: It can resolve where you originally bound your event listeners, regardless of if you used jQuery or whatever. So, either set up a breakpoint or establish an Event Listener Breakpoint[1] and you can walk back to where you registered the handler.
[1]: https://developers.google.com/chrome-developer-tools/docs/ja...
All: one reason we ask you to email us at hn@ycombinator.com instead of posting about [dead] comments here is that it guarantees that we'll see the question. I only saw this by accident 10 hours later. There are too many threads for us to read them all.
You can just say "hard"
[1] https://code.google.com/p/chromium/issues/detail?id=272416
youtube and other "feature-rich" sites work only with massive stuttering for me, so I'm happy for any gif instead of a video which needs to be set up and torn down for every play.
(Yeah, no idea why an editor killed this comment. :/ Thanks folz!)
With it, you can use Chrome Dev Tools to debug your nodejs app.
Right now, we're doing a bunch of work (hah) on our worker support. We'll address pausing execution in workers as well. Expect good improvements and file a ticket at crbug.com for any other ideas, please!
https://github.com/paulmillr/console-polyfill/blob/master/in...
More visually, check out the Before/After images from the doc: http://imgur.com/rZlgrMe
Is HN really so focused on front end that this particular topic finds itself rapidly at the top of news feed and staying there for an extended amount of time?
Has there been a recent poll about topics active HN viewers deem as important? If it really is this JS heavy, that is intriguing.
Don't you think it's more novel than being some trick only relevant to front end web development work?
There's an ongoing, full-time poll, based on voting up posts.
