<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/css" href="/stylesheets/rss.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>Talk Like A Duck: Tag evangelism</title>
    <link>http://talklikeaduck.denhaven2.com/articles/tag/evangelism</link>
    <language>en-us</language>
    <ttl>40</ttl>
    <description>In Ruby, it's not the dog, it's the tricks!</description>
    <item>
      <title>Good News</title>
      <description>Recently  on gluttonous, Kevin Clark announced that &lt;a href="http://glu.ttono.us/articles/2007/06/21/powerset-to-launch-front-end-on-ruby"&gt;
Powerset is going to launch their front-end on Ruby.&lt;/a&gt; It seems that they were already pre-disposed to a major ruby comitment having built a sizable Ruby talent pool for their internal applications.
&lt;p&gt;Prior to making the final decision to go all out with ruby for their front-end launch, the did some due diligence which included investigating the facts behind the recent furore caused by an &lt;a href="Twitter&#8217;s lead developer, Blaine Cook,"&gt;interview&lt;/a&gt; with one of Twitter&amp;#8217;s developers.&lt;/p&gt;
&lt;p&gt;So they went to 
Twitter&#8217;s lead developer, &lt;a href="http://www.slideshare.net/Blaine/scaling-twitter"&gt;Blaine Cook&lt;/a&gt; to get the straight dope.&lt;/p&gt;&lt;p&gt;Quoting Kevin:
&lt;blockquote&gt;The simple fact is that Ruby wasn&#8217;t the source of Twitter&#8217;s woes. As it often happens with rapidly growing sites, they ran into architectural problems. Some design decisions don&#8217;t hurt until they reach a massive scale and at that point you have to rethink your approach. In an email he writes:
&lt;blockquote&gt;
    For us, it&#8217;s really about scaling horizontally &amp;#8211; to that end, Rails and Ruby haven&#8217;t been stumbling blocks, compared to any other language or framework. The performance boosts associated with a &#8220;faster&#8221; language would give us a 10-20% improvement, but thanks to architectural changes that Ruby and Rails happily accommodated, Twitter is 10000% faster than it was in January
&lt;/blockquote&gt;
&lt;/blockquote&gt;
&lt;p&gt;That last sounds quite true and corresponds to my experiences in the past with Smalltalk.  I used to tell &lt;span class="caps"&gt;IBM&lt;/span&gt; customers that almost all performance comes not from the language but from application design, and that using a dynamic language which allowed the application to be developed in what&amp;#8217;s now called an agile development process allows major performance gains through refining, refactoring, and retuning the system as both business and performance requirements get uncovered/discovered.&lt;/p&gt;&lt;p&gt;
That&amp;#8217;s as least as true of Ruby as it was of Smalltalk 15-20 years ago.&lt;/p&gt;</description>
      <pubDate>Fri, 22 Jun 2007 10:29:00 -0400</pubDate>
      <guid isPermaLink="false">urn:uuid:26814954-7ba2-4b21-bb89-8ed609dacb89</guid>
      <author>Rick DeNatale</author>
      <link>http://talklikeaduck.denhaven2.com/articles/2007/06/22/good-news</link>
      <category>ruby</category>
      <category>war_stories</category>
      <category>best_practices</category>
      <category>performance</category>
      <category>evangelism</category>
      <category>rails</category>
      <trackback:ping>http://talklikeaduck.denhaven2.com/articles/trackback/435</trackback:ping>
    </item>
  </channel>
</rss>
