<?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: Complain to me, baby</title>
	<atom:link href="http://www.bitstampede.com/2007/10/07/complain-to-me-baby/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.bitstampede.com/2007/10/07/complain-to-me-baby/</link>
	<description>Bits on the rampage: Eric Shepherd's blog.</description>
	<lastBuildDate>Wed, 08 Sep 2010 09:12:25 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Nickolay Ponomarev</title>
		<link>http://www.bitstampede.com/2007/10/07/complain-to-me-baby/comment-page-1/#comment-41715</link>
		<dc:creator>Nickolay Ponomarev</dc:creator>
		<pubDate>Mon, 08 Oct 2007 21:32:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.bitstampede.com/2007/10/07/complain-to-me-baby/#comment-41715</guid>
		<description>http://developer.mozilla.org/en/docs/XPCNativeWrapper confuses many people, even though it&#039;s very precise. I keep seeing people who think they need to wrap JS objects (when accessing content from extensions) in order to do what they want (typically unsafely access content JS objects). We could use a lighter article that uses less precise and simpler language, perhaps organized as a FAQ and with examples. The original page probably shouldn&#039;t be mucked with though, since it&#039;s easy to change meaning inadvertently and it&#039;s important to have precise explanation of what&#039;s going on.</description>
		<content:encoded><![CDATA[<p><a href="http://developer.mozilla.org/en/docs/XPCNativeWrapper" rel="nofollow">http://developer.mozilla.org/en/docs/XPCNativeWrapper</a> confuses many people, even though it&#8217;s very precise. I keep seeing people who think they need to wrap JS objects (when accessing content from extensions) in order to do what they want (typically unsafely access content JS objects). We could use a lighter article that uses less precise and simpler language, perhaps organized as a FAQ and with examples. The original page probably shouldn&#8217;t be mucked with though, since it&#8217;s easy to change meaning inadvertently and it&#8217;s important to have precise explanation of what&#8217;s going on.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff Walden</title>
		<link>http://www.bitstampede.com/2007/10/07/complain-to-me-baby/comment-page-1/#comment-41632</link>
		<dc:creator>Jeff Walden</dc:creator>
		<pubDate>Mon, 08 Oct 2007 09:48:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.bitstampede.com/2007/10/07/complain-to-me-baby/#comment-41632</guid>
		<description>(Zounds, different layout!)

I direct you to &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=398777&quot; rel=&quot;nofollow&quot;&gt;bug 398777&lt;/a&gt;, which I filed a few days ago over some not-quite-precise, not-quite-informative, not-too-useful documentation that needs expansion and clarification.  :-)</description>
		<content:encoded><![CDATA[<p>(Zounds, different layout!)</p>
<p>I direct you to <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=398777" rel="nofollow">bug 398777</a>, which I filed a few days ago over some not-quite-precise, not-quite-informative, not-too-useful documentation that needs expansion and clarification.  :-)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
