<?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: Is Ruby on Rails a Silver Bullet?</title>
	<atom:link href="http://www.paulbutcher.com/2007/04/ruby-on-rails/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.paulbutcher.com/2007/04/ruby-on-rails/</link>
	<description></description>
	<lastBuildDate>Wed, 12 May 2010 14:44:07 +0100</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Sam Halliday</title>
		<link>http://www.paulbutcher.com/2007/04/ruby-on-rails/comment-page-1/#comment-7</link>
		<dc:creator>Sam Halliday</dc:creator>
		<pubDate>Tue, 14 Aug 2007 08:07:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.texperts.com/2007/04/05/ruby-on-rails/#comment-7</guid>
		<description>It&#039;s interesting to note that Bruce Tate and Justin Gehtland wrote an app in 4 months in Java, then ported to Ruby in four days. Note that I said &quot;ported&quot; not &quot;wrote&quot;. After 4 months of discovering the architectural bugs and learning the traps and pitfalls of a program... rewriting it should be a breeze! Still, 4 nights is bloody fast.</description>
		<content:encoded><![CDATA[<p>It&#8217;s interesting to note that Bruce Tate and Justin Gehtland wrote an app in 4 months in Java, then ported to Ruby in four days. Note that I said &#8220;ported&#8221; not &#8220;wrote&#8221;. After 4 months of discovering the architectural bugs and learning the traps and pitfalls of a program&#8230; rewriting it should be a breeze! Still, 4 nights is bloody fast.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John</title>
		<link>http://www.paulbutcher.com/2007/04/ruby-on-rails/comment-page-1/#comment-6</link>
		<dc:creator>John</dc:creator>
		<pubDate>Sun, 27 May 2007 15:38:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.texperts.com/2007/04/05/ruby-on-rails/#comment-6</guid>
		<description>Nice article. One word: WebObjects. If you know this Rails is &quot;meh&quot;, if you don&#039;t Rails is GOD!</description>
		<content:encoded><![CDATA[<p>Nice article. One word: WebObjects. If you know this Rails is &#8220;meh&#8221;, if you don&#8217;t Rails is GOD!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: There might just be a Silver Bullet &#171; 3Spoken</title>
		<link>http://www.paulbutcher.com/2007/04/ruby-on-rails/comment-page-1/#comment-5</link>
		<dc:creator>There might just be a Silver Bullet &#171; 3Spoken</dc:creator>
		<pubDate>Tue, 10 Apr 2007 07:02:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.texperts.com/2007/04/05/ruby-on-rails/#comment-5</guid>
		<description>[...] I&#8217;ve been using Ruby on Rails on and off for several months and it really does seem to help web application productivity. If you want to read why it successfully contradicts Fred Brooks assertion that there can be no more Silver Bullets, then there is an excellent article just published by 82ASK which states that Rails addresses the new problems inherent in Web application development and does it better than most. [...]</description>
		<content:encoded><![CDATA[<p>[...] I&#8217;ve been using Ruby on Rails on and off for several months and it really does seem to help web application productivity. If you want to read why it successfully contradicts Fred Brooks assertion that there can be no more Silver Bullets, then there is an excellent article just published by 82ASK which states that Rails addresses the new problems inherent in Web application development and does it better than most. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bruce Tate</title>
		<link>http://www.paulbutcher.com/2007/04/ruby-on-rails/comment-page-1/#comment-4</link>
		<dc:creator>Bruce Tate</dc:creator>
		<pubDate>Fri, 06 Apr 2007 14:20:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.texperts.com/2007/04/05/ruby-on-rails/#comment-4</guid>
		<description>Fantastic article. You have said it better than I. I&#039;ve since taken a CTO role at a company called WellGood, LLC, the makers of ChangingThePresent.org. We&#039;ve come to understand that Rails can make a dramatic difference in our overall productivity. It can&#039;t improve our business processes.

Said another way, if technology is your bottleneck, Rails will rock your world. In this spirit, Rails has been very good to us. It&#039;s very close to a silver bullet in that sense. We&#039;re simply applying a more appropriate technology to the task at hand.

But technology usually isn&#039;t the bottleneck. So in some cases, we make bad decisions, and actually dig a hole faster than before. All in all, we&#039;re good enough from a process perspective, and we have a close enough problem to the ideal Rails niche, that we&#039;re able to be very productive.</description>
		<content:encoded><![CDATA[<p>Fantastic article. You have said it better than I. I&#8217;ve since taken a CTO role at a company called WellGood, LLC, the makers of ChangingThePresent.org. We&#8217;ve come to understand that Rails can make a dramatic difference in our overall productivity. It can&#8217;t improve our business processes.</p>
<p>Said another way, if technology is your bottleneck, Rails will rock your world. In this spirit, Rails has been very good to us. It&#8217;s very close to a silver bullet in that sense. We&#8217;re simply applying a more appropriate technology to the task at hand.</p>
<p>But technology usually isn&#8217;t the bottleneck. So in some cases, we make bad decisions, and actually dig a hole faster than before. All in all, we&#8217;re good enough from a process perspective, and we have a close enough problem to the ideal Rails niche, that we&#8217;re able to be very productive.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jerzy prekurat</title>
		<link>http://www.paulbutcher.com/2007/04/ruby-on-rails/comment-page-1/#comment-3</link>
		<dc:creator>jerzy prekurat</dc:creator>
		<pubDate>Thu, 05 Apr 2007 21:02:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.texperts.com/2007/04/05/ruby-on-rails/#comment-3</guid>
		<description>My initial lack of enthusiasm towards RoR was based exactly on &quot;No Silver Bullet&quot; way of thinking: tools do not address essential difficulties of the problem, most tools address accidental difficulties well enough, so what is the big deal ? YAT, YAT, YAT... (yet another tool)

Well, there is something: it works....

I think this article comes long way towards answering - why it works and where it works. Thanks !

jerzy</description>
		<content:encoded><![CDATA[<p>My initial lack of enthusiasm towards RoR was based exactly on &#8220;No Silver Bullet&#8221; way of thinking: tools do not address essential difficulties of the problem, most tools address accidental difficulties well enough, so what is the big deal ? YAT, YAT, YAT&#8230; (yet another tool)</p>
<p>Well, there is something: it works&#8230;.</p>
<p>I think this article comes long way towards answering &#8211; why it works and where it works. Thanks !</p>
<p>jerzy</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ilan berci</title>
		<link>http://www.paulbutcher.com/2007/04/ruby-on-rails/comment-page-1/#comment-2</link>
		<dc:creator>ilan berci</dc:creator>
		<pubDate>Thu, 05 Apr 2007 15:43:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.texperts.com/2007/04/05/ruby-on-rails/#comment-2</guid>
		<description>Simply fantastic artile, (I especially appreciate all the links to the referenced articles!)  I agree with you a 100% in the fact that rails provides benefit by simply addressing accidental difficulties but that is what they stated from the very start (as long as you stay on the path and follow their sensical conventions).

Likewise, it obviously won&#039;t improve efficiency in addressing your bussiness model (which framework does) and never make such claims.  You need Ruby for that!  :)

Thank you for taking the time to write this, I will forward it to my development group.

ilan</description>
		<content:encoded><![CDATA[<p>Simply fantastic artile, (I especially appreciate all the links to the referenced articles!)  I agree with you a 100% in the fact that rails provides benefit by simply addressing accidental difficulties but that is what they stated from the very start (as long as you stay on the path and follow their sensical conventions).</p>
<p>Likewise, it obviously won&#8217;t improve efficiency in addressing your bussiness model (which framework does) and never make such claims.  You need Ruby for that!  <img src='http://www.paulbutcher.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Thank you for taking the time to write this, I will forward it to my development group.</p>
<p>ilan</p>
]]></content:encoded>
	</item>
</channel>
</rss>
