I agree this would be sexy and seems like where we should go, but it's a long term thing. chromedevtools was only my list of things to eventually (ha) play with.
I would think surely browsers would end up with a standard debug protocol at some point--maybe Chrome/GWT could help drive that effort kinda like Chrome with sourcemaps has. As a fun tangent, think about hot swap--would be sweet to send updated JS down to the client in real-time. But how would that communication even work? In Java, even "anonymous" classes have names, so you can say "here the new byte code for Foo$1". How would you say "here is the new JS for closure ...um, *that one*"? - Stephen -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
