<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Safari&#8217;s Web Inspector</title>
	<atom:link href="http://rossboucher.com/2008/04/21/safari-web-inspector/feed/" rel="self" type="application/rss+xml" />
	<link>http://rossboucher.com/2008/04/21/safari-web-inspector/</link>
	<description>Blog by Ross</description>
	<lastBuildDate>Mon, 07 Jun 2010 10:54:39 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: James Prudente</title>
		<link>http://rossboucher.com/2008/04/21/safari-web-inspector/comment-page-1/#comment-576</link>
		<dc:creator>James Prudente</dc:creator>
		<pubDate>Sat, 07 Jun 2008 18:10:50 +0000</pubDate>
		<guid isPermaLink="false">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&#039;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>
