<?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: Soylent Green Is People!</title>
	<atom:link href="http://starkravingfinkle.org/blog/2008/04/soylent-green-is-people/feed/" rel="self" type="application/rss+xml" />
	<link>http://starkravingfinkle.org/blog/2008/04/soylent-green-is-people/</link>
	<description></description>
	<pubDate>Wed, 20 Aug 2008 09:34:20 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: Daniel</title>
		<link>http://starkravingfinkle.org/blog/2008/04/soylent-green-is-people/#comment-5881</link>
		<dc:creator>Daniel</dc:creator>
		<pubDate>Mon, 14 Apr 2008 04:08:52 +0000</pubDate>
		<guid isPermaLink="false">http://starkravingfinkle.org/blog/2008/04/soylent-green-is-people/#comment-5881</guid>
		<description>Well, I don't like to make it ignore for all of my extensions, so if I find an incompatible extension, I decide if I *really* need it, then if I do I manually compatibilize it:

http://daniel1992.wordpress.com/2008/02/03/how-to-install-incompatible-addons-in-firefox-3/

This makes sure that I don't run too many non-compatible extensions, and I know always which ones are and aren't compatible.

Daniel</description>
		<content:encoded><![CDATA[<p>Well, I don&#8217;t like to make it ignore for all of my extensions, so if I find an incompatible extension, I decide if I *really* need it, then if I do I manually compatibilize it:</p>
<p><a href="http://daniel1992.wordpress.com/2008/02/03/how-to-install-incompatible-addons-in-firefox-3/" rel="nofollow">http://daniel1992.wordpress.com/2008/02/03/how-to-install-incompatible-addons-in-firefox-3/</a></p>
<p>This makes sure that I don&#8217;t run too many non-compatible extensions, and I know always which ones are and aren&#8217;t compatible.</p>
<p>Daniel</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nightly Tester Tools Make Your Extensions Work with the Firefox 3 Beta &#124; arthuran.net</title>
		<link>http://starkravingfinkle.org/blog/2008/04/soylent-green-is-people/#comment-5843</link>
		<dc:creator>Nightly Tester Tools Make Your Extensions Work with the Firefox 3 Beta &#124; arthuran.net</dc:creator>
		<pubDate>Thu, 10 Apr 2008 17:57:32 +0000</pubDate>
		<guid isPermaLink="false">http://starkravingfinkle.org/blog/2008/04/soylent-green-is-people/#comment-5843</guid>
		<description>[...] ??????????????? Mark Finkle ???????? Platform Evangelist ??? Mozilla ????????????????????????????????? ?????????? blog ?????????????????????????... [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] ??????????????? Mark Finkle ???????? Platform Evangelist ??? Mozilla ????????????????????????????????? ?????????? blog ?????????????????????????&#8230; [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Fitchet</title>
		<link>http://starkravingfinkle.org/blog/2008/04/soylent-green-is-people/#comment-5818</link>
		<dc:creator>Scott Fitchet</dc:creator>
		<pubDate>Wed, 09 Apr 2008 13:15:53 +0000</pubDate>
		<guid isPermaLink="false">http://starkravingfinkle.org/blog/2008/04/soylent-green-is-people/#comment-5818</guid>
		<description>Good post. I've been using the V3 betas for quite awhile and am still missing a lot of my favorite extensions. :(

( like google toolbar ! )</description>
		<content:encoded><![CDATA[<p>Good post. I&#8217;ve been using the V3 betas for quite awhile and am still missing a lot of my favorite extensions. <img src='http://starkravingfinkle.org/blog/wp-includes/images/smilies/icon_sad.gif' alt=':(' class='wp-smiley' /> </p>
<p>( like google toolbar ! )</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jesse Andrews</title>
		<link>http://starkravingfinkle.org/blog/2008/04/soylent-green-is-people/#comment-5810</link>
		<dc:creator>Jesse Andrews</dc:creator>
		<pubDate>Wed, 09 Apr 2008 05:44:11 +0000</pubDate>
		<guid isPermaLink="false">http://starkravingfinkle.org/blog/2008/04/soylent-green-is-people/#comment-5810</guid>
		<description>&#60;rant&#62;

As a long time extension developer (and previously a developer on Flock), I understand that versioning is important.

That said, I think Mozilla has dropped the ball on coordinating releases and extension support.

1) Extension developers have no time to test/update their extensions before mozilla software updates occur.

2) Because mozilla has code freezes for each release, but they appear to not mean anything (large changes are committed after the freeze, thus extension developers get no head start)

3) After uploading a new release to addons.mozilla.org it can take multiple days to a week for an editors review and users being able to get the update.

4) Users of the addon have no insight into any of this, and blame the extension developers because mozilla's story is "extension developers need to update their extension."

There is no acknowledgement that the developer might be keeping up to date, testing, contributing patches and new features to firefox 3, and uploading a new version to addons.mozilla.org as soon as they are allowed - only to have 1 week of waiting in line for some editor to spend a few minutes looking at your extension.

&#60;/rant&#62;

Will extension developers be given a chance to update their extension on addons.mozilla.org to say they are compatible with 3.0 before the world gets the official firefox 3 release?  Will addons editors be able to review updates in a timely manner?

Or is it business as usually - changes until the last minute, and ship it with a broken extension experience because of the lack of coordination?</description>
		<content:encoded><![CDATA[<p>&lt;rant&gt;</p>
<p>As a long time extension developer (and previously a developer on Flock), I understand that versioning is important.</p>
<p>That said, I think Mozilla has dropped the ball on coordinating releases and extension support.</p>
<p>1) Extension developers have no time to test/update their extensions before mozilla software updates occur.</p>
<p>2) Because mozilla has code freezes for each release, but they appear to not mean anything (large changes are committed after the freeze, thus extension developers get no head start)</p>
<p>3) After uploading a new release to addons.mozilla.org it can take multiple days to a week for an editors review and users being able to get the update.</p>
<p>4) Users of the addon have no insight into any of this, and blame the extension developers because mozilla&#8217;s story is &#8220;extension developers need to update their extension.&#8221;</p>
<p>There is no acknowledgement that the developer might be keeping up to date, testing, contributing patches and new features to firefox 3, and uploading a new version to addons.mozilla.org as soon as they are allowed - only to have 1 week of waiting in line for some editor to spend a few minutes looking at your extension.</p>
<p>&lt;/rant&gt;</p>
<p>Will extension developers be given a chance to update their extension on addons.mozilla.org to say they are compatible with 3.0 before the world gets the official firefox 3 release?  Will addons editors be able to review updates in a timely manner?</p>
<p>Or is it business as usually - changes until the last minute, and ship it with a broken extension experience because of the lack of coordination?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Henrik Nystrom</title>
		<link>http://starkravingfinkle.org/blog/2008/04/soylent-green-is-people/#comment-5809</link>
		<dc:creator>Henrik Nystrom</dc:creator>
		<pubDate>Wed, 09 Apr 2008 05:04:27 +0000</pubDate>
		<guid isPermaLink="false">http://starkravingfinkle.org/blog/2008/04/soylent-green-is-people/#comment-5809</guid>
		<description>Totally agree, to often you read that there is an extension that updates other broken extensions to work with new versions of FF.

Wouldn't it be a good idea to convince the author of the "Nightly Tester Tools" extension to change the phrasing in the tool from “Make compatible” to "Bypass compatibility check". 

Even if it still might be a bad idea to do that (bypass check that is), it might make less people believe that it does some kind of magic voodoo on incompatible extensions.</description>
		<content:encoded><![CDATA[<p>Totally agree, to often you read that there is an extension that updates other broken extensions to work with new versions of FF.</p>
<p>Wouldn&#8217;t it be a good idea to convince the author of the &#8220;Nightly Tester Tools&#8221; extension to change the phrasing in the tool from “Make compatible” to &#8220;Bypass compatibility check&#8221;. </p>
<p>Even if it still might be a bad idea to do that (bypass check that is), it might make less people believe that it does some kind of magic voodoo on incompatible extensions.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Asa Dotzler</title>
		<link>http://starkravingfinkle.org/blog/2008/04/soylent-green-is-people/#comment-5808</link>
		<dc:creator>Asa Dotzler</dc:creator>
		<pubDate>Wed, 09 Apr 2008 04:11:38 +0000</pubDate>
		<guid isPermaLink="false">http://starkravingfinkle.org/blog/2008/04/soylent-green-is-people/#comment-5808</guid>
		<description>Kenguru, a very many of the most popular extensions (perhaps even a majority by usage) do have binary components and they are pretty much guaranteed to crash Firefox if they're allowed to load against the wishes of the compatibility checks. 

- A</description>
		<content:encoded><![CDATA[<p>Kenguru, a very many of the most popular extensions (perhaps even a majority by usage) do have binary components and they are pretty much guaranteed to crash Firefox if they&#8217;re allowed to load against the wishes of the compatibility checks. </p>
<p>- A</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Craig Overend</title>
		<link>http://starkravingfinkle.org/blog/2008/04/soylent-green-is-people/#comment-5805</link>
		<dc:creator>Craig Overend</dc:creator>
		<pubDate>Tue, 08 Apr 2008 20:24:30 +0000</pubDate>
		<guid isPermaLink="false">http://starkravingfinkle.org/blog/2008/04/soylent-green-is-people/#comment-5805</guid>
		<description>I rely on UI and productivity changing extensions that I hate doing without... and are reluctantly not upgrading until they're supported. Do you know if there's an extension that can check which extensions I have installed in FF2 are compatible with FF3? If so, why isn't such a tool included with FF? :)</description>
		<content:encoded><![CDATA[<p>I rely on UI and productivity changing extensions that I hate doing without&#8230; and are reluctantly not upgrading until they&#8217;re supported. Do you know if there&#8217;s an extension that can check which extensions I have installed in FF2 are compatible with FF3? If so, why isn&#8217;t such a tool included with FF? <img src='http://starkravingfinkle.org/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kenguru</title>
		<link>http://starkravingfinkle.org/blog/2008/04/soylent-green-is-people/#comment-5804</link>
		<dc:creator>Kenguru</dc:creator>
		<pubDate>Tue, 08 Apr 2008 19:30:18 +0000</pubDate>
		<guid isPermaLink="false">http://starkravingfinkle.org/blog/2008/04/soylent-green-is-people/#comment-5804</guid>
		<description>I thought that it shouldn't be possible for add-ons to crash the browser (unless the add-on has binary components).  Isn't this true ... ?  

(Of course you are right that incompatible add-ons should not be installed blindly. I am just curious ... )</description>
		<content:encoded><![CDATA[<p>I thought that it shouldn&#8217;t be possible for add-ons to crash the browser (unless the add-on has binary components).  Isn&#8217;t this true &#8230; ?  </p>
<p>(Of course you are right that incompatible add-ons should not be installed blindly. I am just curious &#8230; )</p>
]]></content:encoded>
	</item>
</channel>
</rss>
