Google Chrome’s Developer Tools Improve

blog.chromium.org

62 points·stanleydrew··10 comments

I love the second comment on the post. I can't imagine a tenth of what Google has to deal with every day.

Google seems to have an internal myth that all customers are "that guy" and that therefore the only solution to customer support is /dev/null.

I hoping for this just last night, when I was happily debugging in Chrome but had to switch to Safari for it's richer debugging tools.

The most interesting thing to me about Google at the moment is their pace, hopefully they can maintain it.

Wasn't long ago that Chrome was announced and bare bones. And now it has many if not all the features of the competitors, without the baggage.

Are these improvements added via Chrome or are they improvements to the WebKit Inspector?

Since it's been added to the Chromium project, then even if they haven't pushed it upstream to WebKit, WebKit can always pull it from downstream if they want it.

Granted, it may not be that simple since Chrome uses V8 for its Javascript VM, and these features likely tie directly into V8 abilities that may not be available in the basic WebKit package.

Or maybe I'm talking from ignorance. Please let me know if I am.

The majority of these features have already existed in the upstream WebKit Inspector for several years, but because they ripped out the original javascript implementation to replace with V8, the Chrome people couldn't use any of it.

What would be great is the ability to edit javascript and then save the edited file somewhere. Otherwise I can see alot of copy and paste in my future!

Does anyone here know why the scrolling speed in osx is not as smooth as safari?

The ability to edit the JavaScript will go a long way to make debugging easier.

Reply on news.ycombinator.com