<?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/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:dtvmedia="http://participatoryculture.org/RSSModules/dtv/1.0"
	xmlns:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments on: For Browser Extensions, Grease is the Word</title>
	<atom:link href="http://softwareas.com/for-browser-extensions-grease-is-the-word/feed" rel="self" type="application/rss+xml" />
	<link>http://softwareas.com/for-browser-extensions-grease-is-the-word</link>
	<description>Mahemoff's Podcast/Blog - Web, Programming, Usability from the Author of 'Ajax Design Patterns' (AjaxPatterns.org)</description>
	<lastBuildDate>Tue, 16 Mar 2010 19:17:45 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.3</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: &#187; Mozilla Bespin Meetup FND&#8217;s Blag: Just Another Personal Wobsite</title>
		<link>http://softwareas.com/for-browser-extensions-grease-is-the-word/comment-page-1#comment-421058</link>
		<dc:creator>&#187; Mozilla Bespin Meetup FND&#8217;s Blag: Just Another Personal Wobsite</dc:creator>
		<pubDate>Wed, 11 Mar 2009 08:54:10 +0000</pubDate>
		<guid isPermaLink="false">http://softwareas.com/?p=488#comment-421058</guid>
		<description>&lt;p&gt;[...] Ubiquity as Firefox extension API On a slightly unrelated note, it has been suggested that Ubiquity might be integrated into Firefox, which in turn could lead to a pure-JavaScript API for extensions (currently writing Firefox extensions involves a lot of overhead, e.g. creating XML documents). That would of course be most welcome! [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] Ubiquity as Firefox extension API On a slightly unrelated note, it has been suggested that Ubiquity might be integrated into Firefox, which in turn could lead to a pure-JavaScript API for extensions (currently writing Firefox extensions involves a lot of overhead, e.g. creating XML documents). That would of course be most welcome! [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anamai.net &#187; Blog Archive &#187; Greasemonkey, Chrome Edition</title>
		<link>http://softwareas.com/for-browser-extensions-grease-is-the-word/comment-page-1#comment-375313</link>
		<dc:creator>Anamai.net &#187; Blog Archive &#187; Greasemonkey, Chrome Edition</dc:creator>
		<pubDate>Mon, 10 Nov 2008 22:15:26 +0000</pubDate>
		<guid isPermaLink="false">http://softwareas.com/?p=488#comment-375313</guid>
		<description>&lt;p&gt;[...] be extended to form a more comprehensive extension platform. It will be interesting to see if, as I speculated on my blog today, this patch is to be the seed for Google’s overall approach to Chrome [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] be extended to form a more comprehensive extension platform. It will be interesting to see if, as I speculated on my blog today, this patch is to be the seed for Google’s overall approach to Chrome [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ajaxian &#187; Greasemonkey, Chrome Edition</title>
		<link>http://softwareas.com/for-browser-extensions-grease-is-the-word/comment-page-1#comment-360619</link>
		<dc:creator>Ajaxian &#187; Greasemonkey, Chrome Edition</dc:creator>
		<pubDate>Mon, 20 Oct 2008 22:09:18 +0000</pubDate>
		<guid isPermaLink="false">http://softwareas.com/?p=488#comment-360619</guid>
		<description>&lt;p&gt;[...] be extended to form a more comprehensive extension platform. It will be interesting to see if, as I speculated on my blog today, this patch is to be the seed for Google&#8217;s overall approach to Chrome [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] be extended to form a more comprehensive extension platform. It will be interesting to see if, as I speculated on my blog today, this patch is to be the seed for Google&#8217;s overall approach to Chrome [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mahemoff</title>
		<link>http://softwareas.com/for-browser-extensions-grease-is-the-word/comment-page-1#comment-360592</link>
		<dc:creator>mahemoff</dc:creator>
		<pubDate>Mon, 20 Oct 2008 21:46:36 +0000</pubDate>
		<guid isPermaLink="false">http://softwareas.com/?p=488#comment-360592</guid>
		<description>&lt;p&gt;Xavier, I believe (a) can be overcome simply by giving scripters the APIs to talk to the chrome. And wrt (b), I would rather have an architecture that starts small and extends upward than start with the giant beast (ok I&#039;m exaggerating) and make it overkill for the multitude of simple apps. Even with the current Greasemonkey technology, you can write a complex app by simply pulling down extra code using On-Demand Javascript. An enhanced version of Greasemonkey might let you declare dependencies, which would automatically download. The main point is, whether 1 file or 100, it&#039;s all just plain old Javascript.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Xavier, I believe (a) can be overcome simply by giving scripters the APIs to talk to the chrome. And wrt (b), I would rather have an architecture that starts small and extends upward than start with the giant beast (ok I&#8217;m exaggerating) and make it overkill for the multitude of simple apps. Even with the current Greasemonkey technology, you can write a complex app by simply pulling down extra code using On-Demand Javascript. An enhanced version of Greasemonkey might let you declare dependencies, which would automatically download. The main point is, whether 1 file or 100, it&#8217;s all just plain old Javascript.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: xavier</title>
		<link>http://softwareas.com/for-browser-extensions-grease-is-the-word/comment-page-1#comment-360405</link>
		<dc:creator>xavier</dc:creator>
		<pubDate>Mon, 20 Oct 2008 17:01:59 +0000</pubDate>
		<guid isPermaLink="false">http://softwareas.com/?p=488#comment-360405</guid>
		<description>&lt;p&gt;XPI is overkill for lots of things, and it has lots of room for  simplification... but 
a) there are good extensions that do not target loaded documents but the chome itself 
b) there are good extensions that are document-oriented, but require a level of complexity that hardly makes sense to pack inside a single script file (or that even uses native code)&lt;/p&gt;

&lt;p&gt;Out-of-the-box userscript support is a huge step towards empowering users to shape the web, but doesn&#039;t do much towards what I perceive as google&#039;s vision of the browser-is-the-os.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>XPI is overkill for lots of things, and it has lots of room for  simplification&#8230; but<br />
a) there are good extensions that do not target loaded documents but the chome itself<br />
b) there are good extensions that are document-oriented, but require a level of complexity that hardly makes sense to pack inside a single script file (or that even uses native code)</p>
<p>Out-of-the-box userscript support is a huge step towards empowering users to shape the web, but doesn&#8217;t do much towards what I perceive as google&#8217;s vision of the browser-is-the-os.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: FND</title>
		<link>http://softwareas.com/for-browser-extensions-grease-is-the-word/comment-page-1#comment-360320</link>
		<dc:creator>FND</dc:creator>
		<pubDate>Mon, 20 Oct 2008 14:56:50 +0000</pubDate>
		<guid isPermaLink="false">http://softwareas.com/?p=488#comment-360320</guid>
		<description>&lt;p&gt;I couldn&#039;t agree more - creating an XPI is a major pain compared to simply writing a few lines code.
Let&#039;s hope Mozilla will realize this soon.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I couldn&#8217;t agree more &#8211; creating an XPI is a major pain compared to simply writing a few lines code.<br />
Let&#8217;s hope Mozilla will realize this soon.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
