Chrome DevTools outside of the browser
kenneth.io
Chrome DevTools outside of the browser
1–10 of 30 posts
Re: Chrome DevTools outside of the browser
#2From the authors philosophical standpoint, I think this is indeed very interesting. I hate having to open up multiple instances of the dev tools since they are tied to the tab instance.
Re: Chrome DevTools outside of the browser
#3This seems like a really interesting idea, since I'm not by a computer right now, has anyone played around with it yet? How does it seem?
Re: Chrome DevTools outside of the browser
#4This is really neat.
FYI to run Chrome in remote debugging mode on a Mac
> /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --remote-debugging-port=9222Re: Chrome DevTools outside of the browser
#5How 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...
Re: Chrome DevTools outside of the browser
#6This looks super interesting, and I'm definitely going to try it out when I'm back at home.
GitHub repo if anyone is interested (with install instructions): https://github.com/auchenberg/chrome-devtools-app
Re: Chrome DevTools outside of the browser
#7How scalable is Node these days, considering that javascript has no real multi-threading support, and most of the things you do for a user in Node are thus blocking other users?
I know it is possible to run things in different processes, but it seems to me that this is kind of a hassle (like a workaround).
Re: Chrome DevTools outside of the browser
#8How 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...
This 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.
Re: Chrome DevTools outside of the browser
#9How scalable is Node these days, considering that javascript has no real multi-threading support, and most of the things you do for a user in Node are thus blocking other users? I know it is possible to run things in different processes, but it seems to me that this is kind of a hassle (like a workaround).
Most of the things you do for a user are not blocking, that's the whole point of node. Instead of blocking, almost everything is done with asynchronous callbacks.
Re: Chrome DevTools outside of the browser
#10> Chrome DevTools is close to a functional editor.
Yes, we need this badly! Can't wait to see what we can do with the devtools and make something similar to Brackets!