<?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: Failure</title>
	<atom:link href="http://clubtroppo.com.au/2007/12/14/failure/feed/" rel="self" type="application/rss+xml" />
	<link>http://clubtroppo.com.au/2007/12/14/failure/</link>
	<description></description>
	<pubDate>Sat, 22 Nov 2008 06:24:12 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Jacques Chester</title>
		<link>http://clubtroppo.com.au/2007/12/14/failure/#comment-211279</link>
		<dc:creator>Jacques Chester</dc:creator>
		<pubDate>Sat, 15 Dec 2007 05:24:37 +0000</pubDate>
		<guid isPermaLink="false">http://clubtroppo.com.au/?p=4687#comment-211279</guid>
		<description>cam;


I actually have tooled around some erlang code, in a vain attempt to avoid scaling problems a bit. The problem is that a lot of my problems with Wordpress are institutional -- part of how the project operates. There's more that should be done than I can do.</description>
		<content:encoded><![CDATA[<p>cam;</p>
<p>I actually have tooled around some erlang code, in a vain attempt to avoid scaling problems a bit. The problem is that a lot of my problems with Wordpress are institutional &#8212; part of how the project operates. There&#8217;s more that should be done than I can do.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jacques Chester</title>
		<link>http://clubtroppo.com.au/2007/12/14/failure/#comment-211277</link>
		<dc:creator>Jacques Chester</dc:creator>
		<pubDate>Sat, 15 Dec 2007 05:17:49 +0000</pubDate>
		<guid isPermaLink="false">http://clubtroppo.com.au/?p=4687#comment-211277</guid>
		<description>&lt;blockquote&gt;Problems with WP are mostly the fault of users fiddling with it, using plugins which have not been adequately tested or installed, badly designed themes which are not fully IE/Firefox compatible, or additional layers such as K2.&lt;/blockquote&gt;

Your experiences have differed from mine. I have come across genuine boneheaded bugs. The worst part is when they are in the bug tracker marked closed with worksforme. I have come across two such bugs in just the last few days, including the aforementioned forkbomb yesterday.

Essentially you are saying that if we're prepared to give up plugins everything will be hunky-dorey. You'd be right, though that just avoids the issue by trading away the major selling point of Wordpress.

Let me say that again: the major selling point for Wordpress is not Wordpress. It is the ecosystem around Wordpress. The program itself is not that good, and the project that runs it pay lip service only to fixing bugs. And yes, I do read the mailing list and use the bugtracker. It still doesn't help.</description>
		<content:encoded><![CDATA[<blockquote><p>Problems with WP are mostly the fault of users fiddling with it, using plugins which have not been adequately tested or installed, badly designed themes which are not fully IE/Firefox compatible, or additional layers such as K2.</p></blockquote>
<p>Your experiences have differed from mine. I have come across genuine boneheaded bugs. The worst part is when they are in the bug tracker marked closed with worksforme. I have come across two such bugs in just the last few days, including the aforementioned forkbomb yesterday.</p>
<p>Essentially you are saying that if we&#8217;re prepared to give up plugins everything will be hunky-dorey. You&#8217;d be right, though that just avoids the issue by trading away the major selling point of Wordpress.</p>
<p>Let me say that again: the major selling point for Wordpress is not Wordpress. It is the ecosystem around Wordpress. The program itself is not that good, and the project that runs it pay lip service only to fixing bugs. And yes, I do read the mailing list and use the bugtracker. It still doesn&#8217;t help.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sans Blog</title>
		<link>http://clubtroppo.com.au/2007/12/14/failure/#comment-211108</link>
		<dc:creator>Sans Blog</dc:creator>
		<pubDate>Fri, 14 Dec 2007 21:28:40 +0000</pubDate>
		<guid isPermaLink="false">http://clubtroppo.com.au/?p=4687#comment-211108</guid>
		<description>I have installed and maintained many WP blogs and do not agree with what you say about WordPress. I have also been an IT professional since 1969. 

Problems with WP are mostly the fault of users fiddling with it, using plugins which have not been adequately tested or installed, badly designed themes which are not fully IE/Firefox compatible, or additional layers such as K2.

The real problem with blogs such as Troppo, LP etc. lies in the poor choice of web hosts (usually chosen on price alone) and other hardware 'solutions'. This is exacerbated by well-meaning amateurs administering the hardware and/or software.

Notice that LP is running without problems in exile at Wordpress.com because no one can fiddle with the software and it is running on professional hardware selected to take the load.</description>
		<content:encoded><![CDATA[<p>I have installed and maintained many WP blogs and do not agree with what you say about WordPress. I have also been an IT professional since 1969. </p>
<p>Problems with WP are mostly the fault of users fiddling with it, using plugins which have not been adequately tested or installed, badly designed themes which are not fully IE/Firefox compatible, or additional layers such as K2.</p>
<p>The real problem with blogs such as Troppo, LP etc. lies in the poor choice of web hosts (usually chosen on price alone) and other hardware &#8217;solutions&#8217;. This is exacerbated by well-meaning amateurs administering the hardware and/or software.</p>
<p>Notice that LP is running without problems in exile at Wordpress.com because no one can fiddle with the software and it is running on professional hardware selected to take the load.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: cam</title>
		<link>http://clubtroppo.com.au/2007/12/14/failure/#comment-211089</link>
		<dc:creator>cam</dc:creator>
		<pubDate>Fri, 14 Dec 2007 19:48:44 +0000</pubDate>
		<guid isPermaLink="false">http://clubtroppo.com.au/?p=4687#comment-211089</guid>
		<description>You are left no choice but to write your own blog software in lisp. I suggest you run it as emacs on the server with a clubtroppo blog plugin. 

Only smelly hippies from MIT can be trusted now.</description>
		<content:encoded><![CDATA[<p>You are left no choice but to write your own blog software in lisp. I suggest you run it as emacs on the server with a clubtroppo blog plugin. </p>
<p>Only smelly hippies from MIT can be trusted now.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark U</title>
		<link>http://clubtroppo.com.au/2007/12/14/failure/#comment-211039</link>
		<dc:creator>Mark U</dc:creator>
		<pubDate>Fri, 14 Dec 2007 14:21:21 +0000</pubDate>
		<guid isPermaLink="false">http://clubtroppo.com.au/?p=4687#comment-211039</guid>
		<description>Perhaps you should take Harry Clarke's advice.

http://kalimna.blogspot.com/2007/12/keeping-it-simple-computers-blogging.html</description>
		<content:encoded><![CDATA[<p>Perhaps you should take Harry Clarke&#8217;s advice.</p>
<p><a href="http://kalimna.blogspot.com/2007/12/keeping-it-simple-computers-blogging.html" >http://kalimna.blogspot.com/2007/12/keeping-it-simple-computers-blogging.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Patrick</title>
		<link>http://clubtroppo.com.au/2007/12/14/failure/#comment-211033</link>
		<dc:creator>Patrick</dc:creator>
		<pubDate>Fri, 14 Dec 2007 13:55:52 +0000</pubDate>
		<guid isPermaLink="false">http://clubtroppo.com.au/?p=4687#comment-211033</guid>
		<description>Thanks Jacques - you know we love you for it, if that is any consolation :)</description>
		<content:encoded><![CDATA[<p>Thanks Jacques - you know we love you for it, if that is any consolation <img src='http://clubtroppo.com.au/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
</channel>
</rss>
