<?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: Tim&#8217;s comment challenge&#8230;</title>
	<atom:link href="http://www.sitepoint.com/blogs/2006/05/23/tims-comment-challenge/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sitepoint.com/blogs/2006/05/23/tims-comment-challenge/</link>
	<description></description>
	<pubDate>Sun, 07 Sep 2008 21:10:24 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: David Merrill</title>
		<link>http://www.sitepoint.com/blogs/2006/05/23/tims-comment-challenge/#comment-26200</link>
		<dc:creator>David Merrill</dc:creator>
		<pubDate>Thu, 25 May 2006 13:19:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=1547#comment-26200</guid>
		<description>Tim may be thinking what I've been thinking. I've designed a moderated comments system (Perl with a dash of Ajax) for newspaper web sites. Just hoisted it up the flagpole as a proof of concept, to gauge whether anyone's interested enough to make it worth writing the admin interface. No database software involved, just Perl and a buncha text files on the server. Elemental, like my brain.
http://www.orenews.com/internal/comments/CommentsOnYourSite.html</description>
		<content:encoded><![CDATA[<p>Tim may be thinking what I&#8217;ve been thinking. I&#8217;ve designed a moderated comments system (Perl with a dash of Ajax) for newspaper web sites. Just hoisted it up the flagpole as a proof of concept, to gauge whether anyone&#8217;s interested enough to make it worth writing the admin interface. No database software involved, just Perl and a buncha text files on the server. Elemental, like my brain.<br />
<a href="http://www.orenews.com/internal/comments/CommentsOnYourSite.html" rel="nofollow">http://www.orenews.com/internal/comments/CommentsOnYourSite.html</a></p>]]></content:encoded>
	</item>
	<item>
		<title>By: OfficeOfTheLaw</title>
		<link>http://www.sitepoint.com/blogs/2006/05/23/tims-comment-challenge/#comment-25792</link>
		<dc:creator>OfficeOfTheLaw</dc:creator>
		<pubDate>Wed, 24 May 2006 15:19:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=1547#comment-25792</guid>
		<description>Rasmus's no MVC MVC is fun for the fact that all of his examples point to a "Sorry, we could not find the function blah blah" on php.net.</description>
		<content:encoded><![CDATA[<p>Rasmus&#8217;s no MVC MVC is fun for the fact that all of his examples point to a &#8220;Sorry, we could not find the function blah blah&#8221; on php.net.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Tijs</title>
		<link>http://www.sitepoint.com/blogs/2006/05/23/tims-comment-challenge/#comment-25337</link>
		<dc:creator>Tijs</dc:creator>
		<pubDate>Mon, 22 May 2006 21:28:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=1547#comment-25337</guid>
		<description>He could integrate akismet's anti spam system (http://akismet.com/development/), on my wordpress blog this filters out 99% of the spam</description>
		<content:encoded><![CDATA[<p>He could integrate akismet&#8217;s anti spam system (http://akismet.com/development/), on my wordpress blog this filters out 99% of the spam</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Ivo Jansch</title>
		<link>http://www.sitepoint.com/blogs/2006/05/23/tims-comment-challenge/#comment-25325</link>
		<dc:creator>Ivo Jansch</dc:creator>
		<pubDate>Mon, 22 May 2006 20:11:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=1547#comment-25325</guid>
		<description>If learning a new technology is the key point here, use rails, regardless of the overhead. That's irrelevant.

If you don't care about learning a new tech, but do care about overhead, just don't reinvent the comment wheel and download something that works out of the box.</description>
		<content:encoded><![CDATA[<p>If learning a new technology is the key point here, use rails, regardless of the overhead. That&#8217;s irrelevant.</p>
<p>If you don&#8217;t care about learning a new tech, but do care about overhead, just don&#8217;t reinvent the comment wheel and download something that works out of the box.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://www.sitepoint.com/blogs/2006/05/23/tims-comment-challenge/#comment-25312</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Mon, 22 May 2006 18:36:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=1547#comment-25312</guid>
		<description>&lt;blockquote&gt;related point—where do we point him for help installing PEAR if needed&lt;/blockquote&gt;

http://pear.php.net/manual/en/installation.php</description>
		<content:encoded><![CDATA[<blockquote><p>related point—where do we point him for help installing PEAR if needed</p></blockquote>
<p><a href="http://pear.php.net/manual/en/installation.php" rel="nofollow">http://pear.php.net/manual/en/installation.php</a></p>]]></content:encoded>
	</item>
	<item>
		<title>By: Fenrir2</title>
		<link>http://www.sitepoint.com/blogs/2006/05/23/tims-comment-challenge/#comment-25290</link>
		<dc:creator>Fenrir2</dc:creator>
		<pubDate>Mon, 22 May 2006 17:50:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=1547#comment-25290</guid>
		<description>A simple Ruby script as CGI would be good, or maybe the Camping Microframework? (but even that would be an overkill).

I would use a Ruby script if I could install it on a host. Use YAML instead of XML, it's much easier than XML (even more easier than PHP's XML, even SIMPLExml):
&lt;code&gt;
comments = YAML.load('the-file')&lt;/code&gt;

To load the file into a Ruby array/hash, and:

&lt;code&gt;comments.to_yaml&lt;/code&gt;

To convert it back to YAML. I wouldn't use Javascript to convert this to HTML, but I would let Ruby do that. Javascript could load the comments with Ajax, or in a frame (or maybe inline in the page).

But if you want to use PHP:

- No forms library, overkill, too much to learn for a beginner
- Markdown, or if that gives your users too much power, PHP's equivalent of Rails' simple_format()
- OpenID seems ok
- No MVC MVC is excellent for this (small) script. Or just a file with MVC separated by database function library, controller code on top of php-file, template after the controller code.
- SimpleXML is simpler, and he doesn't need advanced things (and you could use xpath for that), so I'd use that. Or just vanilla-inline-PHP for XML generation.
- Of course, there are languages like Ruby/Python/Javascript/Perl/Lua that are (IMHO) much more sane than PHP, but because most webhosts have PHP pre-installed, it might be better for a small script.</description>
		<content:encoded><![CDATA[<p>A simple Ruby script as CGI would be good, or maybe the Camping Microframework? (but even that would be an overkill).</p>
<p>I would use a Ruby script if I could install it on a host. Use YAML instead of XML, it&#8217;s much easier than XML (even more easier than PHP&#8217;s XML, even SIMPLExml):<br />
<code>
comments = YAML.load('the-file')</code></p>
<p>To load the file into a Ruby array/hash, and:</p>
<code>comments.to_yaml</code>
<p>To convert it back to YAML. I wouldn&#8217;t use Javascript to convert this to HTML, but I would let Ruby do that. Javascript could load the comments with Ajax, or in a frame (or maybe inline in the page).</p>
<p>But if you want to use PHP:</p>
<p>- No forms library, overkill, too much to learn for a beginner<br />
- Markdown, or if that gives your users too much power, PHP&#8217;s equivalent of Rails&#8217; simple_format()<br />
- OpenID seems ok<br />
- No MVC MVC is excellent for this (small) script. Or just a file with MVC separated by database function library, controller code on top of php-file, template after the controller code.<br />
- SimpleXML is simpler, and he doesn&#8217;t need advanced things (and you could use xpath for that), so I&#8217;d use that. Or just vanilla-inline-PHP for XML generation.<br />
- Of course, there are languages like Ruby/Python/Javascript/Perl/Lua that are (IMHO) much more sane than PHP, but because most webhosts have PHP pre-installed, it might be better for a small script.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Andi</title>
		<link>http://www.sitepoint.com/blogs/2006/05/23/tims-comment-challenge/#comment-25287</link>
		<dc:creator>Andi</dc:creator>
		<pubDate>Mon, 22 May 2006 17:39:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=1547#comment-25287</guid>
		<description>Well I wrote a very simple one-file-one-table-only PHP solution. Just a few lines of code to integrate. Even comes with a capture mechanism and &lt;a href="http://gravatar.com" rel="nofollow"&gt;Gravatar support&lt;/a&gt;. Nothing fancy, no special text formatting (except URLs) but does it's job. Have a look at the &lt;a href="http://www.splitbrain.org/projects/my_two_cents" rel="nofollow"&gt;My Two Cents (MTC)&lt;/a&gt; comment system.</description>
		<content:encoded><![CDATA[<p>Well I wrote a very simple one-file-one-table-only PHP solution. Just a few lines of code to integrate. Even comes with a capture mechanism and <a href="http://gravatar.com" rel="nofollow">Gravatar support</a>. Nothing fancy, no special text formatting (except URLs) but does it&#8217;s job. Have a look at the <a href="http://www.splitbrain.org/projects/my_two_cents" rel="nofollow">My Two Cents (MTC)</a> comment system.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan Bates</title>
		<link>http://www.sitepoint.com/blogs/2006/05/23/tims-comment-challenge/#comment-25283</link>
		<dc:creator>Ryan Bates</dc:creator>
		<pubDate>Mon, 22 May 2006 17:02:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=1547#comment-25283</guid>
		<description>I agree that Rails may be a little over-kill for something so simple (especially if he's not using a database), but how about just a Ruby script? Althought it may not be the best tool for the job, if he is intersted in learning Rails in the future, I think learning Ruby first and getting comfortable with that is the way to go. It really is an amazing and elegant language all on its own. It's what got me first looking into Rails, and I'm very glad I did.</description>
		<content:encoded><![CDATA[<p>I agree that Rails may be a little over-kill for something so simple (especially if he&#8217;s not using a database), but how about just a Ruby script? Althought it may not be the best tool for the job, if he is intersted in learning Rails in the future, I think learning Ruby first and getting comfortable with that is the way to go. It really is an amazing and elegant language all on its own. It&#8217;s what got me first looking into Rails, and I&#8217;m very glad I did.</p>]]></content:encoded>
	</item>
</channel>
</rss>
