<?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, Ruby, and Scaling</title>
	<atom:link href="http://laughingmeme.org/2007/04/12/twitter-ruby-and-scaling/feed/" rel="self" type="application/rss+xml" />
	<link>http://laughingmeme.org/2007/04/12/twitter-ruby-and-scaling/</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Wed, 10 Mar 2010 15:18:40 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: What Second Life can teach about scaling - Laughing Meme</title>
		<link>http://laughingmeme.org/2007/04/12/twitter-ruby-and-scaling/comment-page-1/#comment-810745</link>
		<dc:creator>What Second Life can teach about scaling - Laughing Meme</dc:creator>
		<pubDate>Thu, 04 Feb 2010 01:00:16 +0000</pubDate>
		<guid isPermaLink="false">http://laughingmeme.org/2007/04/12/twitter-ruby-and-scaling/#comment-810745</guid>
		<description>&lt;p&gt;[...] Wanted to jump up and down when I read this. Building it &#8220;right&#8221; the first time is one of the best guarantees of failure I know. Scaling is always a catch up game. [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] Wanted to jump up and down when I read this. Building it &#8220;right&#8221; the first time is one of the best guarantees of failure I know. Scaling is always a catch up game. [...]</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Twiiter Outage?</title>
		<link>http://laughingmeme.org/2007/04/12/twitter-ruby-and-scaling/comment-page-1/#comment-154823</link>
		<dc:creator>Twiiter Outage?</dc:creator>
		<pubDate>Fri, 16 Nov 2007 17:30:23 +0000</pubDate>
		<guid isPermaLink="false">http://laughingmeme.org/2007/04/12/twitter-ruby-and-scaling/#comment-154823</guid>
		<description>&lt;p&gt;[...] I think Ruby&#8217;s edges (or core maybe) are showing here.&#160; This has been discussed at length at Laughing Meme, but I haven&#8217;t seen much about this subject on Twitter&#8217;s blog.&#160; Lots of folks are using Ruby daily, with many of them adopting Rails, and all of them have a stake in its future. [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] I think Ruby&#8217;s edges (or core maybe) are showing here.&nbsp; This has been discussed at length at Laughing Meme, but I haven&#8217;t seen much about this subject on Twitter&#8217;s blog.&nbsp; Lots of folks are using Ruby daily, with many of them adopting Rails, and all of them have a stake in its future. [...]</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Rails woes. The slow that is keeping twitter down. &#187; Harper Reed: Tech, Phones, Yo-yoing and Death Metal</title>
		<link>http://laughingmeme.org/2007/04/12/twitter-ruby-and-scaling/comment-page-1/#comment-33097</link>
		<dc:creator>Rails woes. The slow that is keeping twitter down. &#187; Harper Reed: Tech, Phones, Yo-yoing and Death Metal</dc:creator>
		<pubDate>Mon, 16 Apr 2007 06:04:40 +0000</pubDate>
		<guid isPermaLink="false">http://laughingmeme.org/2007/04/12/twitter-ruby-and-scaling/#comment-33097</guid>
		<description>&lt;p&gt;[...] I think some of the best points on this whole thing is the following (paraphrased from somewhere 1, 2, 3):  Rails is great because it trades developer performance for framework performance. Rails is good enough for almost every application. However, if you get big enough - rails will suffer. If you are writing an app that may get big, you may want to choose a different framework. [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] I think some of the best points on this whole thing is the following (paraphrased from somewhere 1, 2, 3):  Rails is great because it trades developer performance for framework performance. Rails is good enough for almost every application. However, if you get big enough &#8211; rails will suffer. If you are writing an app that may get big, you may want to choose a different framework. [...]</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Warren Seen &#187; Blog Archive &#187; Rails, Twitter and the 800lb Gorilla in the Room&#8230;</title>
		<link>http://laughingmeme.org/2007/04/12/twitter-ruby-and-scaling/comment-page-1/#comment-33010</link>
		<dc:creator>Warren Seen &#187; Blog Archive &#187; Rails, Twitter and the 800lb Gorilla in the Room&#8230;</dc:creator>
		<pubDate>Mon, 16 Apr 2007 01:25:08 +0000</pubDate>
		<guid isPermaLink="false">http://laughingmeme.org/2007/04/12/twitter-ruby-and-scaling/#comment-33010</guid>
		<description>&lt;p&gt;[...] If perchance, you&#8217;re part of the other 1%, you should be thrilled to have this problem, it means your software has been successful! Fact is, you don&#8217;t accidentally create a site/service which generates 11,000+ requests/sec. You explicitly set out to do so. And presumably, you chose Rails for a reason. Why shouldn&#8217;t we extend the concept of &#8220;no premature optimisation&#8221; to language and platform selection? If Twitter had chosen an &#8220;enterprise&#8221; class platform and tried to architect for 11k reqs/sec, chances are they would still be building&#8230; [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] If perchance, you&#8217;re part of the other 1%, you should be thrilled to have this problem, it means your software has been successful! Fact is, you don&#8217;t accidentally create a site/service which generates 11,000+ requests/sec. You explicitly set out to do so. And presumably, you chose Rails for a reason. Why shouldn&#8217;t we extend the concept of &#8220;no premature optimisation&#8221; to language and platform selection? If Twitter had chosen an &#8220;enterprise&#8221; class platform and tried to architect for 11k reqs/sec, chances are they would still be building&#8230; [...]</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Around the web &#124; alexking.org</title>
		<link>http://laughingmeme.org/2007/04/12/twitter-ruby-and-scaling/comment-page-1/#comment-32902</link>
		<dc:creator>Around the web &#124; alexking.org</dc:creator>
		<pubDate>Sun, 15 Apr 2007 17:59:41 +0000</pubDate>
		<guid isPermaLink="false">http://laughingmeme.org/2007/04/12/twitter-ruby-and-scaling/#comment-32902</guid>
		<description>&lt;p&gt;[...] Twitter, Ruby, and Scaling [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] Twitter, Ruby, and Scaling [...]</p>]]></content:encoded>
	</item>
	<item>
		<title>By: lucasjosh.com &#187; Blog Archive &#187; Twitter, Rails and Scaling</title>
		<link>http://laughingmeme.org/2007/04/12/twitter-ruby-and-scaling/comment-page-1/#comment-32016</link>
		<dc:creator>lucasjosh.com &#187; Blog Archive &#187; Twitter, Rails and Scaling</dc:creator>
		<pubDate>Fri, 13 Apr 2007 14:03:07 +0000</pubDate>
		<guid isPermaLink="false">http://laughingmeme.org/2007/04/12/twitter-ruby-and-scaling/#comment-32016</guid>
		<description>&lt;p&gt;[...] More thoughts from Rafe and Kellan. Kellan ends with:  You&#8217;ll never build a successful site if you build to scale from day 1, scaling is always a catch up game, but it&#8217;s the best game there is. [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] More thoughts from Rafe and Kellan. Kellan ends with:  You&rsquo;ll never build a successful site if you build to scale from day 1, scaling is always a catch up game, but it&rsquo;s the best game there is. [...]</p>]]></content:encoded>
	</item>
</channel>
</rss>
