<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.4" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Safari&#8217;s Web Inspector</title>
	<link>http://rossboucher.com/2008/04/21/safari-web-inspector/</link>
	<description>Just another WordPress weblog</description>
	<pubDate>Sun, 12 Oct 2008 10:49:35 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.4</generator>

	<item>
		<title>by: James Prudente</title>
		<link>http://rossboucher.com/2008/04/21/safari-web-inspector/#comment-576</link>
		<pubDate>Sat, 07 Jun 2008 18:10:50 +0000</pubDate>
		<guid>http://rossboucher.com/2008/04/21/safari-web-inspector/#comment-576</guid>
					<description>I just discovered the new debugger in the webkit nightly build.  Has a long ways to go to catch firebug, but I was able to break, walk through code and  dump variables in the console.  

There is also a profiler which I was unable to get to produce actually timings, but it looks like its close to working.

I had the same problems with Drosera (incredibly slow) and found it unusable.  I think next time I have a safari bug to fix I'll give the new inspector a shot.</description>
		<content:encoded><![CDATA[<p>I just discovered the new debugger in the webkit nightly build.  Has a long ways to go to catch firebug, but I was able to break, walk through code and  dump variables in the console.  </p>
<p>There is also a profiler which I was unable to get to produce actually timings, but it looks like its close to working.</p>
<p>I had the same problems with Drosera (incredibly slow) and found it unusable.  I think next time I have a safari bug to fix I&#8217;ll give the new inspector a shot.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.177 seconds -->
