4 ms·
How does this differ from the default Chrome DevTools remote debugging over the wire? Doesn't that also run it's own http server in a way? https://developer.c
by chippy 12y ago
How does this differ from the default Chrome DevTools remote debugging over the wire? Doesn't that also run it's own http server in a way?
https://developer.chrome.com/devtools/docs/debugger-protocol#remote https://developer.chrome.com/devtools/docs/debugger-protocol...
- jaimeyap 12y agoThis is almost certainly using the same protocol. The DevTools team did the work a while back to pull everything they needed out of process and establish the devtools protocol to enable remote debugging. What the author has done is to take the Chrome DevTools (which is already basically a standalone web app), and package it up with Node-webkit as a standalone app. I think this is cool, not from a technical perspective necessarily (since the engineering work was mostly already done by the DevTools team for remote debugging), but rather from a usability perspective. Slight tweak to the UX and it changes the mental framing people have of what the chrome DevTools actually is.
- wildpeaks 12y agoIt does expose a websocket other apps can use to control Chrome (such as this node module: https://github.com/cyrus-and/chrome-remote-interface https://github.com/cyrus-and/chrome-remote-interface or the Chrome webdriver )