Preface: This is quite an opinionated post, and everything here is said without have had a chat with the team, and is purely based upon the observations I’ve made since the announcement and by following the project. I might be completely wrong in my criticism.
Preface: My intention with BrowserRemote is to show-case the powerfullness of exposing remote debugging, in a secure manner, to application developers via an injected API, and to show that remote debugging can be valuable for end-users too.
It’s now 24 hours ago I arrived here in hot Bangkok with just 60 items with me. For the next coming months I’ll be traveling asia, in a somewhat unplanned manner. It’s the first time I’m traveling longer than a month, and the first time I’m on my own.
For a while I’ve been wondering how much work it would be to take Chrome DevTools out of the browser, and into its own app - independent of Chrome.
So about a month ago, where I had a quiet evening in the airport I pulled Chrome DevTools from the git repo, and wrapped the app with node-webkit. A few hours later, after figuring out how node-webkit worked, I had a functional prototype of DevTools as a standalone app.