<?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: Twitter blaming Ruby on Rails for failures?</title>
	<atom:link href="http://www.texasstartupblog.com/2007/04/12/twitter-blaming-ruby-on-rails-for-failures/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.texasstartupblog.com/2007/04/12/twitter-blaming-ruby-on-rails-for-failures/</link>
	<description>Spurring innovation and entrepreneurship.</description>
	<pubDate>Sat, 20 Mar 2010 06:46:02 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Uncertainty for Ruby and Rails despite changes</title>
		<link>http://www.texasstartupblog.com/2007/04/12/twitter-blaming-ruby-on-rails-for-failures/#comment-340492</link>
		<dc:creator>Uncertainty for Ruby and Rails despite changes</dc:creator>
		<pubDate>Thu, 17 Jan 2008 08:00:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.texasstartupblog.com/2007/04/12/twitter-blaming-ruby-on-rails-for-failures/#comment-340492</guid>
		<description>[...] of his site with Ruby on Rails and gone back to PHP scripting. And earlier in the year Twitter blamed Ruby on Rails for degraded performance on its [...]</description>
		<content:encoded><![CDATA[<p>[...] of his site with Ruby on Rails and gone back to PHP scripting. And earlier in the year Twitter blamed Ruby on Rails for degraded performance on its [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ARGH</title>
		<link>http://www.texasstartupblog.com/2007/04/12/twitter-blaming-ruby-on-rails-for-failures/#comment-340468</link>
		<dc:creator>ARGH</dc:creator>
		<pubDate>Thu, 17 Jan 2008 00:10:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.texasstartupblog.com/2007/04/12/twitter-blaming-ruby-on-rails-for-failures/#comment-340468</guid>
		<description>Alex Payne is freaking clueless about scalability, he has all the experience of a new college graduate who wouldn't know scalability if it bit him in the ass. Saying that all the scalability problem lies with Ruby on Rails is like a blind man holding onto an elephant's tail and saying that an elephant is a thin wiry spineless animal.</description>
		<content:encoded><![CDATA[<p>Alex Payne is freaking clueless about scalability, he has all the experience of a new college graduate who wouldn&#8217;t know scalability if it bit him in the ass. Saying that all the scalability problem lies with Ruby on Rails is like a blind man holding onto an elephant&#8217;s tail and saying that an elephant is a thin wiry spineless animal.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave Clark</title>
		<link>http://www.texasstartupblog.com/2007/04/12/twitter-blaming-ruby-on-rails-for-failures/#comment-82137</link>
		<dc:creator>Dave Clark</dc:creator>
		<pubDate>Sun, 15 Apr 2007 09:40:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.texasstartupblog.com/2007/04/12/twitter-blaming-ruby-on-rails-for-failures/#comment-82137</guid>
		<description>To be fair to Ruby on Rails, the article title says "Twitter blaming Ruby on Rails for failures?", yet the quote from Alex is talking about the speed of 'Ruby' - the underlying interpreted language. I make the distinction because if you had a faster Ruby (via various methods now in development), you would not necessarily make any changes to the ROR framework that is running on top of it. Note that Alex didn't say that it was the ROR framework that is slowing them down.</description>
		<content:encoded><![CDATA[<p>To be fair to Ruby on Rails, the article title says &#8220;Twitter blaming Ruby on Rails for failures?&#8221;, yet the quote from Alex is talking about the speed of &#8216;Ruby&#8217; - the underlying interpreted language. I make the distinction because if you had a faster Ruby (via various methods now in development), you would not necessarily make any changes to the ROR framework that is running on top of it. Note that Alex didn&#8217;t say that it was the ROR framework that is slowing them down.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Christopher St. John</title>
		<link>http://www.texasstartupblog.com/2007/04/12/twitter-blaming-ruby-on-rails-for-failures/#comment-81817</link>
		<dc:creator>Christopher St. John</dc:creator>
		<pubDate>Fri, 13 Apr 2007 19:40:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.texasstartupblog.com/2007/04/12/twitter-blaming-ruby-on-rails-for-failures/#comment-81817</guid>
		<description>Ruby is slower than it should be. Rails is more limited in some ways than you'd really like. It's possible to work around these fact by putting extra effort into creative deployment. All of the above statements are true, and it's not playing "the blame game" to acknowledge that Ruby and Rails aren't the most mature language/platform pair around and an awful lot of work needs to be done, especially in making Ruby into a "real" language. (Where "real" is "state of the art in language implementation for the year 2007", which Ruby very definitely isn't.)</description>
		<content:encoded><![CDATA[<p>Ruby is slower than it should be. Rails is more limited in some ways than you&#8217;d really like. It&#8217;s possible to work around these fact by putting extra effort into creative deployment. All of the above statements are true, and it&#8217;s not playing &#8220;the blame game&#8221; to acknowledge that Ruby and Rails aren&#8217;t the most mature language/platform pair around and an awful lot of work needs to be done, especially in making Ruby into a &#8220;real&#8221; language. (Where &#8220;real&#8221; is &#8220;state of the art in language implementation for the year 2007&#8243;, which Ruby very definitely isn&#8217;t.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roj</title>
		<link>http://www.texasstartupblog.com/2007/04/12/twitter-blaming-ruby-on-rails-for-failures/#comment-81684</link>
		<dc:creator>Roj</dc:creator>
		<pubDate>Fri, 13 Apr 2007 05:16:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.texasstartupblog.com/2007/04/12/twitter-blaming-ruby-on-rails-for-failures/#comment-81684</guid>
		<description>There are many who are very passionate about Ruby on Rails - but it may not be the right platform for scaleability.  I am curious what the highest traffic using RoR is...</description>
		<content:encoded><![CDATA[<p>There are many who are very passionate about Ruby on Rails - but it may not be the right platform for scaleability.  I am curious what the highest traffic using RoR is&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: STUFFLEUFAGUS - &#8220;A true friend stabs you in the front&#8221; - Oscar Wilde &#187; Texas Startup Blog: Web 2.0 and Social Media &#187; Blog Archive &#187; Twitter blaming Ruby on Rails for failures?</title>
		<link>http://www.texasstartupblog.com/2007/04/12/twitter-blaming-ruby-on-rails-for-failures/#comment-81661</link>
		<dc:creator>STUFFLEUFAGUS - &#8220;A true friend stabs you in the front&#8221; - Oscar Wilde &#187; Texas Startup Blog: Web 2.0 and Social Media &#187; Blog Archive &#187; Twitter blaming Ruby on Rails for failures?</dc:creator>
		<pubDate>Fri, 13 Apr 2007 01:41:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.texasstartupblog.com/2007/04/12/twitter-blaming-ruby-on-rails-for-failures/#comment-81661</guid>
		<description>[...] You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.       Prev/Next Posts   &#171; O&#8217;Reilly responds to code of conductfeedback &#124; Home       Leave a Reply [...]</description>
		<content:encoded><![CDATA[<p>[...] You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.       Prev/Next Posts   &laquo; O&#8217;Reilly responds to code of conductfeedback | Home       Leave a Reply [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
