<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="/stylesheets/rss.css" type="text/css"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
  <channel>
    <title>Yup Dot Com: Martin Fowler on Ruby</title>
    <link>http://www.yup.com/articles/2006/05/11/martin-fowler-on-ruby</link>
    <language>en-us</language>
    <ttl>40</ttl>
    <description>Advanced Web Services</description>
    <item>
      <title>Martin Fowler on Ruby</title>
      <description>&lt;p&gt;&lt;a href="http://en.wikipedia.org/wiki/Martin_Fowler"&gt;Martin Fowler&lt;/a&gt;, well known in the OO, Patterns, and Agile world, has written a short article about whether Ruby is ready for the mainstream yet, and whether you should be considering it for your projects. He writes,&lt;/p&gt;

&lt;blockquote&gt;
It&amp;#8217;s still early days yet, but I now have a handful of project experiences to draw on. So far the results are firmly in favor of Ruby. When I ask the question &amp;#8220;do you think you&amp;#8217;re significantly more productive in Ruby rather than Java/c#&amp;#8221;, each time I&amp;#8217;ve got a strong &amp;#8216;yes&amp;#8217;. This is enough for me to start saying that for a suitable project, you should give Ruby a spin. Which, of course, only leaves open the small question of what counts as &amp;#8216;suitable&amp;#8217;.
&lt;/blockquote&gt;

&lt;p&gt;Read on for some personal thoughts on Ruby and Ruby on Rails, as well as some bonus graphs from Google Trends.&lt;/p&gt;</description>
      <pubDate>Thu, 11 May 2006 12:59:00 -0400</pubDate>
      <guid isPermaLink="false">urn:uuid:acb19ec5-f3e5-4257-bbf2-df1bf3caecf2</guid>
      <author>Daniel Butler</author>
      <link>http://www.yup.com/articles/2006/05/11/martin-fowler-on-ruby</link>
      <category>Ruby on Rails</category>
      <category>Programming</category>
      <category>mainstream</category>
    </item>
  </channel>
</rss>
