<?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: Rails Rules for the Enterprise</title>
	<atom:link href="http://itsinsider.com/2008/01/29/rails-rules-for-the-enterprise/feed/" rel="self" type="application/rss+xml" />
	<link>http://itsinsider.com/2008/01/29/rails-rules-for-the-enterprise/</link>
	<description>An Insider&#039;s view on IT-Social for the Enterprise</description>
	<lastBuildDate>Tue, 24 Jan 2012 21:55:07 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Andrew Bruce</title>
		<link>http://itsinsider.com/2008/01/29/rails-rules-for-the-enterprise/#comment-248</link>
		<dc:creator>Andrew Bruce</dc:creator>
		<pubDate>Thu, 07 Feb 2008 20:33:41 +0000</pubDate>
		<guid isPermaLink="false">http://susanitsa.wordpress.com/?p=198#comment-248</guid>
		<description>The debate about PHP vs Rails is fascinating.
I am an ex Smalltalk programmer and as such love the who MVC paradigm.  This is what Rails brings to the table.  Through standards it enforces the Model View Controller separation.

Maybe it&#039;s an evolution of languages.  Convoluted C or Fortran programs enforced no separation, although it is perfectly possible to write good elegant procedural code with good standards that makes it maintainable  However, must old procedural language programs were a bear to maintain, and as for separating the UI and placing a different one on top... well good luck.
Maybe Rails is a similar evolution from PHP.  All the point made above are true for PHP, but as Tim points out Rails makes it a heck of a lot easier to be agile and adaptable to different environments and / or UI/s than PHP because of the standardized separation.</description>
		<content:encoded><![CDATA[<p>The debate about PHP vs Rails is fascinating.<br />
I am an ex Smalltalk programmer and as such love the who MVC paradigm.  This is what Rails brings to the table.  Through standards it enforces the Model View Controller separation.</p>
<p>Maybe it&#8217;s an evolution of languages.  Convoluted C or Fortran programs enforced no separation, although it is perfectly possible to write good elegant procedural code with good standards that makes it maintainable  However, must old procedural language programs were a bear to maintain, and as for separating the UI and placing a different one on top&#8230; well good luck.<br />
Maybe Rails is a similar evolution from PHP.  All the point made above are true for PHP, but as Tim points out Rails makes it a heck of a lot easier to be agile and adaptable to different environments and / or UI/s than PHP because of the standardized separation.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

