<?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: my own gallery</title>
	<atom:link href="http://revjim.net/2006/03/31/my-own-gallery/feed/" rel="self" type="application/rss+xml" />
	<link>http://revjim.net/2006/03/31/my-own-gallery/</link>
	<description>because a Reverend can&#039;t be wrong.</description>
	<lastBuildDate>Wed, 09 May 2012 16:43:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
<atom:link rel="hub" href="http://pubsubhubbub.appspot.com"/><atom:link rel="hub" href="http://superfeedr.com/hubbub"/>	<item>
		<title>By: cranialstrain@livejournal.com</title>
		<link>http://revjim.net/2006/03/31/my-own-gallery/comment-page-1/#comment-1952</link>
		<dc:creator>cranialstrain@livejournal.com</dc:creator>
		<pubDate>Fri, 31 Mar 2006 15:27:53 +0000</pubDate>
		<guid isPermaLink="false">http://revjim.net/2006/03/31/my-own-gallery/#comment-1952</guid>
		<description>I suppose it&#039;s down to the old equation of time spent vs &lt;i&gt;long-term&lt;/i&gt; benefits; if you are confident that developing your own custom solution and associated modules will stand the test of time, and perhaps, give you the opportunity to market/dstribute this on - then it seems a good option.

On the other hand, if (for example) a new blogging or gallery s/w becomes available that is in better (astehetically, UI or functionally) than Gallery/WordPress you&#039;re somewhat stuck in the mud considering having to ditch your hard work.

Personally (as you well know) I hate WordPress and I&#039;m not fond of Gallery, but if I did, and felt the end solution would be both functionally and UI-wise superior to anything else available, I would put in the hard work and get something I&#039;m happy with!</description>
		<content:encoded><![CDATA[<p>I suppose it&#8217;s down to the old equation of time spent vs <i>long-term</i> benefits; if you are confident that developing your own custom solution and associated modules will stand the test of time, and perhaps, give you the opportunity to market/dstribute this on &#8211; then it seems a good option.</p>
<p>On the other hand, if (for example) a new blogging or gallery s/w becomes available that is in better (astehetically, UI or functionally) than Gallery/WordPress you&#8217;re somewhat stuck in the mud considering having to ditch your hard work.</p>
<p>Personally (as you well know) I hate WordPress and I&#8217;m not fond of Gallery, but if I did, and felt the end solution would be both functionally and UI-wise superior to anything else available, I would put in the hard work and get something I&#8217;m happy with!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

