I like it. Obviously, I don't expect (or want) Chrome to replace my text editor any time soon, but this will be great for quick fixes.
Firebug/Devtools are obviously ridiculously awesome. For debugging layout, there will never be anything as good as "Inspect element".
But for programming, I want to write/debug in my IDE, and poke the browser via a standardized wire protocol that IE/FF/Chrome/Opera all support.
Not to say they shouldn't be working on this; if this is the workflow you like, that's awesome. I just hope wire protocols get some love too.
With the amazing collective effort going into browsers, hopefully I don't have anything to worry about.
Firefox "marionette" automates (controls) firefox via the WebDriver API: https://developer.mozilla.org/en-US/docs/Marionette
Chrome also has an "automation proxy" API that is used by ChromeDriver. http://code.google.com/p/chromedriver/
Web driver approaches would work much better if there were sane ways to control where the new window pops up. Even on Linux with X Monad or stumpwm, the communication/protocol for the location of new windows popping up is difficult to impossible.
I think it would be great if Google Chrome had an API that allowed any editor to push updates to the browser.
downloads canary immediately