<?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: Six Ways In Which WordPress Could Die</title>
	<atom:link href="http://www.wptavern.com/six-ways-in-which-wordpress-could-die/feed" rel="self" type="application/rss+xml" />
	<link>http://www.wptavern.com/six-ways-in-which-wordpress-could-die</link>
	<description>Where Every Drink Is On The House</description>
	<lastBuildDate>Wed, 08 Feb 2012 10:56:16 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Lastest News &#187; Wptavern.com - A New Kid on the Block in the Wordpress community</title>
		<link>http://www.wptavern.com/six-ways-in-which-wordpress-could-die#comment-1479</link>
		<dc:creator>Lastest News &#187; Wptavern.com - A New Kid on the Block in the Wordpress community</dc:creator>
		<pubDate>Wed, 27 May 2009 06:02:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.wptavern.com/?p=419#comment-1479</guid>
		<description>[...] He doesn&#8217;t always agree with the decision made within the team. One of his posts foresees 6 ways in which Wordpress could die. I cannot be more agreeable with the [...]</description>
		<content:encoded><![CDATA[<p>[...] He doesn&#8217;t always agree with the decision made within the team. One of his posts foresees 6 ways in which WordPress could die. I cannot be more agreeable with the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Heißt die Zukunft von Wordpress Habari? &#124; eliwagar</title>
		<link>http://www.wptavern.com/six-ways-in-which-wordpress-could-die#comment-403</link>
		<dc:creator>Heißt die Zukunft von Wordpress Habari? &#124; eliwagar</dc:creator>
		<pubDate>Tue, 03 Mar 2009 10:53:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.wptavern.com/?p=419#comment-403</guid>
		<description>[...] verwiesen (klar, mal wieder Verweise *st&#246;hn*, aber who the fuck ist Jeff?), der sich in seiner WP Tavern fragt, wie Wordpress sterben wird. Er f&#252;hrt da sechs m&#246;gliche Szenarien auf: Third party [...]</description>
		<content:encoded><![CDATA[<p>[...] verwiesen (klar, mal wieder Verweise *st&#246;hn*, aber who the fuck ist Jeff?), der sich in seiner WP Tavern fragt, wie WordPress sterben wird. Er f&#252;hrt da sechs m&#246;gliche Szenarien auf: Third party [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt</title>
		<link>http://www.wptavern.com/six-ways-in-which-wordpress-could-die#comment-299</link>
		<dc:creator>Matt</dc:creator>
		<pubDate>Sun, 15 Feb 2009 18:07:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.wptavern.com/?p=419#comment-299</guid>
		<description>WordPress will be around and thriving long after I&#039;m gone, and I&#039;m only 25. :)</description>
		<content:encoded><![CDATA[<p>WordPress will be around and thriving long after I&#8217;m gone, and I&#8217;m only 25. :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: links for 2009-02-14 &#124; This Inspires Me</title>
		<link>http://www.wptavern.com/six-ways-in-which-wordpress-could-die#comment-285</link>
		<dc:creator>links for 2009-02-14 &#124; This Inspires Me</dc:creator>
		<pubDate>Sat, 14 Feb 2009 10:16:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.wptavern.com/?p=419#comment-285</guid>
		<description>[...] Six Ways In Which WordPress Could Die (tags: wordpress) [...]</description>
		<content:encoded><![CDATA[<p>[...] Six Ways In Which WordPress Could Die (tags: wordpress) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: that girl again</title>
		<link>http://www.wptavern.com/six-ways-in-which-wordpress-could-die#comment-283</link>
		<dc:creator>that girl again</dc:creator>
		<pubDate>Sat, 14 Feb 2009 03:01:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.wptavern.com/?p=419#comment-283</guid>
		<description>Actually, I&#039;ve always thought that the main reason MT got overtaken by WP was that PHP is &lt;strike&gt;better&lt;/strike&gt; generally more user-friendly than Perl ;) If it hadn&#039;t been wordpress, it would have been some other PHP-based platform. Budget webhosts were more likely to offer PHP support than Perl, and to offer automated installation of PHP software. The licencing screwup just speeded up the process.

Therefore if another framework were to overtake PHP in popularity, wordpress would be dead in the water. I have no idea when that will happen but I find it difficult to believe that it never will. Anyway, I have my suspicions that either #4 or #5 will do for them before that happens.</description>
		<content:encoded><![CDATA[<p>Actually, I&#8217;ve always thought that the main reason MT got overtaken by WP was that PHP is <strike>better</strike> generally more user-friendly than Perl ;) If it hadn&#8217;t been wordpress, it would have been some other PHP-based platform. Budget webhosts were more likely to offer PHP support than Perl, and to offer automated installation of PHP software. The licencing screwup just speeded up the process.</p>
<p>Therefore if another framework were to overtake PHP in popularity, wordpress would be dead in the water. I have no idea when that will happen but I find it difficult to believe that it never will. Anyway, I have my suspicions that either #4 or #5 will do for them before that happens.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brad</title>
		<link>http://www.wptavern.com/six-ways-in-which-wordpress-could-die#comment-282</link>
		<dc:creator>Brad</dc:creator>
		<pubDate>Fri, 13 Feb 2009 21:48:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.wptavern.com/?p=419#comment-282</guid>
		<description>Security is my number one fear and the same for most I think.  WP did have an exploit that let a lot of websites get hacked.  I have a few clients that were hit (before my services of course :P) and lost all of their data.

If WordPress suffers a larger hack that infects hundreds of thousands of websites I think most mainstream users will run horrified to another platform.

Another good reason to stay current on updates :)

Nice post Jeff, very thought provoking!  Looking forward to the podcast tonight, should be frEAkY!</description>
		<content:encoded><![CDATA[<p>Security is my number one fear and the same for most I think.  WP did have an exploit that let a lot of websites get hacked.  I have a few clients that were hit (before my services of course :P) and lost all of their data.</p>
<p>If WordPress suffers a larger hack that infects hundreds of thousands of websites I think most mainstream users will run horrified to another platform.</p>
<p>Another good reason to stay current on updates :)</p>
<p>Nice post Jeff, very thought provoking!  Looking forward to the podcast tonight, should be frEAkY!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Six million ways to die: choose one - WP FUN</title>
		<link>http://www.wptavern.com/six-ways-in-which-wordpress-could-die#comment-281</link>
		<dc:creator>Six million ways to die: choose one - WP FUN</dc:creator>
		<pubDate>Fri, 13 Feb 2009 19:43:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.wptavern.com/?p=419#comment-281</guid>
		<description>[...] million ways to die: choose one So Jeff wants to know how WordPress will die. Well, seeing as he asked, I will tell you. WordPress is already dead, its just that no one has [...]</description>
		<content:encoded><![CDATA[<p>[...] million ways to die: choose one So Jeff wants to know how WordPress will die. Well, seeing as he asked, I will tell you. WordPress is already dead, its just that no one has [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tekzt</title>
		<link>http://www.wptavern.com/six-ways-in-which-wordpress-could-die#comment-280</link>
		<dc:creator>tekzt</dc:creator>
		<pubDate>Fri, 13 Feb 2009 17:28:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.wptavern.com/?p=419#comment-280</guid>
		<description>@&lt;a href=&quot;#comment-272&quot; rel=&quot;nofollow&quot;&gt;Angsuman Chakraborty&lt;/a&gt; - There is no need for Wordpress to cooperate with commercial WP Developers. The developer would be the one who benefits through it, not wordpress or the wordpress community. They have their own developers who not only develop wordpress but also some of the plugins, which are considered &quot;third party&quot;, cause they are released by the persons and not through automattic. 

If they had money issues they would cut the wordpress.com-stats plugin for .org users which runs on wordpress.com and would remove pingomatic as a default service (or strip pingomatic itself down to a lesser server load). that would cut some major costs.

Automattic doesn´t keep you from developing for wordpress. It´s very accessable for any developer. They just don´t want to host stuff of you if you´re an commercial developer and have link to your commercial site in the foorer. That´s perfectly ok with me, because even if the plugin on their site is free, it´s advertising. Just because its not on the wordpress site doesnt mean you can´t get word about your plugins out there. 

@&lt;a href=&quot;#comment-279&quot; rel=&quot;nofollow&quot;&gt;jeremyclarke&lt;/a&gt; - That´s true, sometimes they forget to listen *coughtinymcecough*</description>
		<content:encoded><![CDATA[<p>@<a href="#comment-272" rel="nofollow">Angsuman Chakraborty</a> &#8211; There is no need for WordPress to cooperate with commercial WP Developers. The developer would be the one who benefits through it, not wordpress or the wordpress community. They have their own developers who not only develop wordpress but also some of the plugins, which are considered &#8220;third party&#8221;, cause they are released by the persons and not through automattic. </p>
<p>If they had money issues they would cut the wordpress.com-stats plugin for .org users which runs on wordpress.com and would remove pingomatic as a default service (or strip pingomatic itself down to a lesser server load). that would cut some major costs.</p>
<p>Automattic doesn´t keep you from developing for wordpress. It´s very accessable for any developer. They just don´t want to host stuff of you if you´re an commercial developer and have link to your commercial site in the foorer. That´s perfectly ok with me, because even if the plugin on their site is free, it´s advertising. Just because its not on the wordpress site doesnt mean you can´t get word about your plugins out there. </p>
<p>@<a href="#comment-279" rel="nofollow">jeremyclarke</a> &#8211; That´s true, sometimes they forget to listen *coughtinymcecough*</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jeremyclarke</title>
		<link>http://www.wptavern.com/six-ways-in-which-wordpress-could-die#comment-279</link>
		<dc:creator>jeremyclarke</dc:creator>
		<pubDate>Fri, 13 Feb 2009 16:52:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.wptavern.com/?p=419#comment-279</guid>
		<description>&lt;blockquote&gt;I was very pleased to hear Matt say in the special interview I conducted with him that the decisions he makes regarding WordPress.org are made with the community in mind. That is exactly what I wanted to hear.&lt;/blockquote&gt;

Not to say that Matt was being dishonest or anything, but watch out with that kind of language! Of course he&#039;s going to say what you want to hear in public! The question is whether it really seemed honest and whether they are actually thinking of the community (which they are IMHO, they just don&#039;t always LISTEN to the community, because they think they know better).</description>
		<content:encoded><![CDATA[<blockquote><p>I was very pleased to hear Matt say in the special interview I conducted with him that the decisions he makes regarding WordPress.org are made with the community in mind. That is exactly what I wanted to hear.</p></blockquote>
<p>Not to say that Matt was being dishonest or anything, but watch out with that kind of language! Of course he&#8217;s going to say what you want to hear in public! The question is whether it really seemed honest and whether they are actually thinking of the community (which they are IMHO, they just don&#8217;t always LISTEN to the community, because they think they know better).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim Child</title>
		<link>http://www.wptavern.com/six-ways-in-which-wordpress-could-die#comment-277</link>
		<dc:creator>Jim Child</dc:creator>
		<pubDate>Fri, 13 Feb 2009 15:55:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.wptavern.com/?p=419#comment-277</guid>
		<description>Thanks for your thoughts, Jeff! You managed to put together a very concise consolidation of the &quot;risks&quot; that WP faces as time goes on.

So now &lt;em&gt;&quot;we&quot;&lt;/em&gt;, and that &lt;strong&gt;should definitely&lt;/strong&gt; include the folks at  WP/Automattic, have a list of things to watch out for. As a loosely knit community we can all make efforts to avoid the known pitfalls.

&lt;strong&gt;WordPress Forever!&lt;/strong&gt;</description>
		<content:encoded><![CDATA[<p>Thanks for your thoughts, Jeff! You managed to put together a very concise consolidation of the &#8220;risks&#8221; that WP faces as time goes on.</p>
<p>So now <em>&#8220;we&#8221;</em>, and that <strong>should definitely</strong> include the folks at  WP/Automattic, have a list of things to watch out for. As a loosely knit community we can all make efforts to avoid the known pitfalls.</p>
<p><strong>WordPress Forever!</strong></p>
]]></content:encoded>
	</item>
</channel>
</rss>

