<?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"
	>
<channel>
	<title>Comments on: GNOME Do and The Network Backed Plugin Architecture</title>
	<atom:link href="http://redmonk.com/sogrady/2008/06/23/network-plugin-architecture/feed/" rel="self" type="application/rss+xml" />
	<link>http://redmonk.com/sogrady/2008/06/23/network-plugin-architecture/</link>
	<description>because technology is just another ecosystem</description>
	<pubDate>Wed, 03 Dec 2008 00:23:29 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: andres</title>
		<link>http://redmonk.com/sogrady/2008/06/23/network-plugin-architecture/#comment-468972</link>
		<dc:creator>andres</dc:creator>
		<pubDate>Sat, 13 Sep 2008 23:02:14 +0000</pubDate>
		<guid isPermaLink="false">http://redmonk.com/sogrady/?p=2076#comment-468972</guid>
		<description>Nice read.  I liked your article. :P</description>
		<content:encoded><![CDATA[<p>Nice read.  I liked your article. <img src='http://redmonk.com/sogrady/wp/wp-includes/images/smilies/icon_razz.gif' alt=':P' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bill Jackson</title>
		<link>http://redmonk.com/sogrady/2008/06/23/network-plugin-architecture/#comment-420387</link>
		<dc:creator>Bill Jackson</dc:creator>
		<pubDate>Sat, 28 Jun 2008 03:16:53 +0000</pubDate>
		<guid isPermaLink="false">http://redmonk.com/sogrady/?p=2076#comment-420387</guid>
		<description>Err... your Firefox 3's Add-ons dialog is modal?  Is that specific to the Linux version or something?  Sounds annoying!  ;)

Anyway, another great example of this model is JetBrains' IntelliJ IDEA; just like with Firefox, the repository is centralized, with some yummy statistics made available, and finding/installing/updating/bug-reporting plugins is well-integrated into the IDE.  My only complaint is that, like Firefox, it still requires a restart to activate changes (and it's far less trivial than restarting Firefox, even if you're like me and tend to have 100+ tabs open at a time).

As for "what took so long", it seems to me that the obstacle for most projects is that this requires one or more people to fill a few different roles:
a) someone with the desire and initiative to actually drive the change,
b) someone to design and implement a reliable browse/search/install/update mechanism,
c) someone to provide infrastructure (paying for hosting or working to get a reliable free-hosting setup, buying a domain name, et cetera),
d) someone to maintain the repository when it is all done.

I think a generic framework could be developed that would take care of (b), (c) isn't much of an obstacle with a little work and tolerance for ugly domains ;), and a bundled management webapp could make (d) trivial.  What do you think?</description>
		<content:encoded><![CDATA[<p>Err&#8230; your Firefox 3&#8217;s Add-ons dialog is modal?  Is that specific to the Linux version or something?  Sounds annoying!  <img src='http://redmonk.com/sogrady/wp/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
<p>Anyway, another great example of this model is JetBrains&#8217; IntelliJ IDEA; just like with Firefox, the repository is centralized, with some yummy statistics made available, and finding/installing/updating/bug-reporting plugins is well-integrated into the IDE.  My only complaint is that, like Firefox, it still requires a restart to activate changes (and it&#8217;s far less trivial than restarting Firefox, even if you&#8217;re like me and tend to have 100+ tabs open at a time).</p>
<p>As for &#8220;what took so long&#8221;, it seems to me that the obstacle for most projects is that this requires one or more people to fill a few different roles:<br />
a) someone with the desire and initiative to actually drive the change,<br />
b) someone to design and implement a reliable browse/search/install/update mechanism,<br />
c) someone to provide infrastructure (paying for hosting or working to get a reliable free-hosting setup, buying a domain name, et cetera),<br />
d) someone to maintain the repository when it is all done.</p>
<p>I think a generic framework could be developed that would take care of (b), (c) isn&#8217;t much of an obstacle with a little work and tolerance for ugly domains ;), and a bundled management webapp could make (d) trivial.  What do you think?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
