<?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: Lightweight vs Heavyweight</title>
	<atom:link href="http://blog.jameshiggs.com/2008/01/02/lightweight-vs-heavyweight/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.jameshiggs.com/2008/01/02/lightweight-vs-heavyweight/</link>
	<description>James Higgs&#039;s Blog</description>
	<lastBuildDate>Thu, 04 Feb 2010 11:36:43 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Why aren&#8217;t you using open source? &#171; I&#8217;m Simon Dickson.</title>
		<link>http://blog.jameshiggs.com/2008/01/02/lightweight-vs-heavyweight/comment-page-1/#comment-27</link>
		<dc:creator>Why aren&#8217;t you using open source? &#171; I&#8217;m Simon Dickson.</dc:creator>
		<pubDate>Wed, 09 Jan 2008 14:41:29 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jameshiggs.com/2008/01/02/lightweight-vs-heavyweight/#comment-27</guid>
		<description>[...] has some interesting thoughts on WordPress itself, incidentally. My own feeling (which won&#8217;t come as any surprise) is that I&#8217;ve been able [...]</description>
		<content:encoded><![CDATA[<p>[...] has some interesting thoughts on WordPress itself, incidentally. My own feeling (which won&#8217;t come as any surprise) is that I&#8217;ve been able [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: higgis</title>
		<link>http://blog.jameshiggs.com/2008/01/02/lightweight-vs-heavyweight/comment-page-1/#comment-26</link>
		<dc:creator>higgis</dc:creator>
		<pubDate>Sun, 06 Jan 2008 18:37:19 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jameshiggs.com/2008/01/02/lightweight-vs-heavyweight/#comment-26</guid>
		<description>I&#039;m going to have to continue to disagree. The scenarios you&#039;ve highlighted are ones where (a) there is a bespoke &#039;heavyweight&#039; system that is fit for purpose and (b) there is a &#039;lightweight&#039; system that is not fit for purpose. These two facts do not inform a discussion about whether lightweight systems are *inherently* worse in some situations that heavyweight ones. I&#039;ll bet there are lightweight CMS systems that could do a good job on the Guardian website. (Incidentally, I wonder how you&#039;re getting on with Movable Type on Comment is Free.)

I expanded the discussion to include heavyweight vs lightweight languages because I didn&#039;t think you were comparing apples to apples - languages are clearly trying to solve exactly the same problem but do so in different ways. WordPress is, despite its claims to be a CMS, a blogging platform and not much more. It&#039;s very good at being a blogging platform. 

I spent 5 years writing and maintaining a CMS/Community Platform - on which we built quite a number of blogs. But if *all* you are doing is a blog, I&#039;d still recommend using WordPress (as I do myself). The comparison you should be doing is between a full-featured but lightweight CMS and your bespoke one. That might be instructive.</description>
		<content:encoded><![CDATA[<p>I&#8217;m going to have to continue to disagree. The scenarios you&#8217;ve highlighted are ones where (a) there is a bespoke &#8216;heavyweight&#8217; system that is fit for purpose and (b) there is a &#8216;lightweight&#8217; system that is not fit for purpose. These two facts do not inform a discussion about whether lightweight systems are *inherently* worse in some situations that heavyweight ones. I&#8217;ll bet there are lightweight CMS systems that could do a good job on the Guardian website. (Incidentally, I wonder how you&#8217;re getting on with Movable Type on Comment is Free.)</p>
<p>I expanded the discussion to include heavyweight vs lightweight languages because I didn&#8217;t think you were comparing apples to apples &#8211; languages are clearly trying to solve exactly the same problem but do so in different ways. WordPress is, despite its claims to be a CMS, a blogging platform and not much more. It&#8217;s very good at being a blogging platform. </p>
<p>I spent 5 years writing and maintaining a CMS/Community Platform &#8211; on which we built quite a number of blogs. But if *all* you are doing is a blog, I&#8217;d still recommend using WordPress (as I do myself). The comparison you should be doing is between a full-featured but lightweight CMS and your bespoke one. That might be instructive.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nik Silver</title>
		<link>http://blog.jameshiggs.com/2008/01/02/lightweight-vs-heavyweight/comment-page-1/#comment-25</link>
		<dc:creator>Nik Silver</dc:creator>
		<pubDate>Fri, 04 Jan 2008 16:01:28 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jameshiggs.com/2008/01/02/lightweight-vs-heavyweight/#comment-25</guid>
		<description>If my article came across as saying heavyweight is better than lightweight, then I failed to communicate what I wanted. I had hoped that at no point I said anything as crude as &quot;A is better than B&quot;, for life isn&#039;t as simple as that. Instead, the article was an attempt to clarify &quot;what lightweight really means, both in terms of benefits and drawbacks&quot;.

The scenarios I walked through should have helped show situations where lightweight systems were not appropriate, not that they never are appropriate. For example, I agree with you that getting ads into a WordPress is perfectly reasonable; indeed I said this: &quot;a lightweight CMS such as WordPress could probably do any one of these things [such as contextual ad inclusion]&quot;. My point there was that anyone would be mistaken if they thought WordPress could be evolved to become the CMS that Guardian Unlimited required, with all the features I listed (and many more I didn&#039;t).

The message of the piece should have been &quot;it&#039;s horses for courses&quot; (not very earth-shattering), and to give a guide as to which courses might be appropriate for the various horses.

By the way, I thought you were very thought-provoking when you contrasted lightweight systems with &quot;enterprise&quot; software. I didn&#039;t use the word &quot;enterprise&quot;, and it made me ask myself the question: What does it mean to be an enterprise system? Does it mean the opposite of lightweight? I&#039;m not sure it does. It&#039;s perfectly possible for a lightweight system to be fit for the enterprise, and I know a number of companies, including my own, which run them and for which they are just the right thing doing just the right job.</description>
		<content:encoded><![CDATA[<p>If my article came across as saying heavyweight is better than lightweight, then I failed to communicate what I wanted. I had hoped that at no point I said anything as crude as &#8220;A is better than B&#8221;, for life isn&#8217;t as simple as that. Instead, the article was an attempt to clarify &#8220;what lightweight really means, both in terms of benefits and drawbacks&#8221;.</p>
<p>The scenarios I walked through should have helped show situations where lightweight systems were not appropriate, not that they never are appropriate. For example, I agree with you that getting ads into a WordPress is perfectly reasonable; indeed I said this: &#8220;a lightweight CMS such as WordPress could probably do any one of these things [such as contextual ad inclusion]&#8220;. My point there was that anyone would be mistaken if they thought WordPress could be evolved to become the CMS that Guardian Unlimited required, with all the features I listed (and many more I didn&#8217;t).</p>
<p>The message of the piece should have been &#8220;it&#8217;s horses for courses&#8221; (not very earth-shattering), and to give a guide as to which courses might be appropriate for the various horses.</p>
<p>By the way, I thought you were very thought-provoking when you contrasted lightweight systems with &#8220;enterprise&#8221; software. I didn&#8217;t use the word &#8220;enterprise&#8221;, and it made me ask myself the question: What does it mean to be an enterprise system? Does it mean the opposite of lightweight? I&#8217;m not sure it does. It&#8217;s perfectly possible for a lightweight system to be fit for the enterprise, and I know a number of companies, including my own, which run them and for which they are just the right thing doing just the right job.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
