<?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: The Wall</title>
	<atom:link href="http://webr3.org/blog/general/the-wall/feed/" rel="self" type="application/rss+xml" />
	<link>http://webr3.org/blog/general/the-wall/</link>
	<description>brain&#039;s on fire!</description>
	<lastBuildDate>Fri, 22 Apr 2011 00:44:37 +0100</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Tim</title>
		<link>http://webr3.org/blog/general/the-wall/comment-page-1/#comment-227</link>
		<dc:creator>Tim</dc:creator>
		<pubDate>Fri, 26 Feb 2010 10:51:16 +0000</pubDate>
		<guid isPermaLink="false">http://webr3.org/blog/?p=144#comment-227</guid>
		<description>Good point, makes one wonder: would starting a FAQ in PHP and then the site evolving from around there lead eventually to reimplementing the whole mega-modular thing later? Would that be better or worse than starting from all the modules, if you end up pulling them in one at a time as required anyway?</description>
		<content:encoded><![CDATA[<p>Good point, makes one wonder: would starting a FAQ in PHP and then the site evolving from around there lead eventually to reimplementing the whole mega-modular thing later? Would that be better or worse than starting from all the modules, if you end up pulling them in one at a time as required anyway?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tonypee</title>
		<link>http://webr3.org/blog/general/the-wall/comment-page-1/#comment-117</link>
		<dc:creator>tonypee</dc:creator>
		<pubDate>Thu, 24 Sep 2009 13:36:41 +0000</pubDate>
		<guid isPermaLink="false">http://webr3.org/blog/?p=144#comment-117</guid>
		<description>HA! couldnt agree more! I think this is the thing that kills java- the culture that everything must be done *properly*. Like all things, its a matter of finding the common ground- Too much focus on coding conventions and patterns causes bloat, while too much php hacking makes for ugly brittle code. Php does bring out the devil in people... i&#039;m sure of it ;P

Its really up to the developer to design with simplicity and the end goal in mind</description>
		<content:encoded><![CDATA[<p>HA! couldnt agree more! I think this is the thing that kills java- the culture that everything must be done *properly*. Like all things, its a matter of finding the common ground- Too much focus on coding conventions and patterns causes bloat, while too much php hacking makes for ugly brittle code. Php does bring out the devil in people... i'm sure of it ;P</p>
<p>Its really up to the developer to design with simplicity and the end goal in mind</p>
]]></content:encoded>
	</item>
</channel>
</rss>

