<?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: What Ruby on Rails Gets Right</title>
	<atom:link href="http://www.jrandolph.com/blog/2005/06/15/what-ruby-on-rails-gets-right/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.jrandolph.com/blog/2005/06/15/what-ruby-on-rails-gets-right/</link>
	<description>software development and testing</description>
	<lastBuildDate>Thu, 24 Apr 2008 12:51:01 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Justin</title>
		<link>http://www.jrandolph.com/blog/2005/06/15/what-ruby-on-rails-gets-right/comment-page-1/#comment-183</link>
		<dc:creator>Justin</dc:creator>
		<pubDate>Mon, 31 Oct 2005 20:13:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.jrandolph.com/blog/?p=2#comment-183</guid>
		<description>For those looking for a &quot;Consumer Reports&quot; for web app frameworks, point your feed readers at &lt;a href=&quot;http://www.servercodex.com/&quot; rel=&quot;nofollow&quot;&gt;Server Codex&lt;/a&gt;. The first of a long-running comparison series on web application frameworks is due to be published in November.</description>
		<content:encoded><![CDATA[<p>For those looking for a &#8220;Consumer Reports&#8221; for web app frameworks, point your feed readers at <a href="http://www.servercodex.com/" rel="nofollow">Server Codex</a>. The first of a long-running comparison series on web application frameworks is due to be published in November.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason Huggins</title>
		<link>http://www.jrandolph.com/blog/2005/06/15/what-ruby-on-rails-gets-right/comment-page-1/#comment-54</link>
		<dc:creator>Jason Huggins</dc:creator>
		<pubDate>Mon, 18 Jul 2005 15:50:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.jrandolph.com/blog/?p=2#comment-54</guid>
		<description>There is more chaos in the Python and Java framework landscape because Python and Java have been more popular for a longer period of time than Ruby. Do not fear, as Ruby becomes more popular, and Rails becomes big and all powerful, Ruby will start to see a proliferation of frameworks, too. Personally, I don&#039;t see the number of choices as bad. It&#039;s up there with that &quot;Long Tail&quot; theory of niche marketing... The car industry has the same problem/situation.... There are a million cars to choose from when you want to buy one, but thankfully there are lots of car sites and magazines to help you pick one you&#039;ll be happy with.

So it would be nice if there was an equivalent of &quot;Car &amp; Driver&quot; or &quot;Consumer Reports&quot; for web app frameworks... Newbies could feel free to only pay attention to the editor&#039;s choice for &quot;Top 10 Frameworks of 2005&quot;. :-) 

Without that kind of &quot;Editor&#039;s Choice&quot;, the act of choosing is a chore. But just because Rails is in Ruby doesn&#039;t make it any easier to choose a framework. Ruby might only have one car to sell (Rails), but it&#039;s still just a car, and you have to compare it against all other cars (frameworks in other languages) to make a choice.

Ian Bicking commented on the language decision-space argument. He noticed that Zope and Rails fans picked the framework first, and the implementation language was secondary. For example, many people are only learning Ruby because of Rails, not the other way around.</description>
		<content:encoded><![CDATA[<p>There is more chaos in the Python and Java framework landscape because Python and Java have been more popular for a longer period of time than Ruby. Do not fear, as Ruby becomes more popular, and Rails becomes big and all powerful, Ruby will start to see a proliferation of frameworks, too. Personally, I don&#8217;t see the number of choices as bad. It&#8217;s up there with that &#8220;Long Tail&#8221; theory of niche marketing&#8230; The car industry has the same problem/situation&#8230;. There are a million cars to choose from when you want to buy one, but thankfully there are lots of car sites and magazines to help you pick one you&#8217;ll be happy with.</p>
<p>So it would be nice if there was an equivalent of &#8220;Car &amp; Driver&#8221; or &#8220;Consumer Reports&#8221; for web app frameworks&#8230; Newbies could feel free to only pay attention to the editor&#8217;s choice for &#8220;Top 10 Frameworks of 2005&#8243;. :-) </p>
<p>Without that kind of &#8220;Editor&#8217;s Choice&#8221;, the act of choosing is a chore. But just because Rails is in Ruby doesn&#8217;t make it any easier to choose a framework. Ruby might only have one car to sell (Rails), but it&#8217;s still just a car, and you have to compare it against all other cars (frameworks in other languages) to make a choice.</p>
<p>Ian Bicking commented on the language decision-space argument. He noticed that Zope and Rails fans picked the framework first, and the implementation language was secondary. For example, many people are only learning Ruby because of Rails, not the other way around.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Bx</title>
		<link>http://www.jrandolph.com/blog/2005/06/15/what-ruby-on-rails-gets-right/comment-page-1/#comment-51</link>
		<dc:creator>Paul Bx</dc:creator>
		<pubDate>Mon, 18 Jul 2005 14:50:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.jrandolph.com/blog/?p=2#comment-51</guid>
		<description>The other factor with Rails, something it sort of gets right by circumstance, is that the Ruby web framework space is not very crowded. Python, on the other hand, has a dozen or more, with no obvious leader.  Malcom Gladwell&#039;s _Blink_ does a nice job of explaining how increased choices impede the act of choosing -- in fact, the more choices we have the more likely we are to choose none of them. I think that the implementation language (Ruby, Python, Java, PHP) defines a sort of decision-space. You look in the Python decision-space and you get dizzy.  You look in the ruby decision-space and you just see Rails. Sold!</description>
		<content:encoded><![CDATA[<p>The other factor with Rails, something it sort of gets right by circumstance, is that the Ruby web framework space is not very crowded. Python, on the other hand, has a dozen or more, with no obvious leader.  Malcom Gladwell&#8217;s <em>Blink</em> does a nice job of explaining how increased choices impede the act of choosing &#8212; in fact, the more choices we have the more likely we are to choose none of them. I think that the implementation language (Ruby, Python, Java, PHP) defines a sort of decision-space. You look in the Python decision-space and you get dizzy.  You look in the ruby decision-space and you just see Rails. Sold!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
