<?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 on Rails FUD</title>
	<atom:link href="http://www.digitalhobbit.com/2008/05/01/twitter-ruby-on-rails-fud/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.digitalhobbit.com/2008/05/01/twitter-ruby-on-rails-fud/</link>
	<description>Thoughts from the Hobbit Hole</description>
	<lastBuildDate>Sun, 05 Sep 2010 11:31:56 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: DigitalHobbit</title>
		<link>http://www.digitalhobbit.com/2008/05/01/twitter-ruby-on-rails-fud/comment-page-1/#comment-72604</link>
		<dc:creator>DigitalHobbit</dc:creator>
		<pubDate>Sun, 10 Aug 2008 07:02:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.digitalhobbit.com/?p=293#comment-72604</guid>
		<description>&lt;p&gt;Hi Zev,&lt;/p&gt;

&lt;p&gt;This is impossible to answer without knowing more about your app. For web apps, I am definitely biased towards productive environments such as Rails (in the Ruby world) or Django (in the Python world), over something like a more heavyweight J2EE stack. But how your app will scale will depend on a lot more than just your choice of web framework. For many social applications (such as Twitter), the website ends up only being a relatively small part of the overall system, and how the rest of the system is architected becomes very important. Is your app componentized in a way that allows you to scale up individual components as demand increases? Are you going to be able to cache the hell out your system to avoid database access? Etc.&lt;/p&gt;

&lt;p&gt;Anyway, good luck with your app!&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Hi Zev,</p>

<p>This is impossible to answer without knowing more about your app. For web apps, I am definitely biased towards productive environments such as Rails (in the Ruby world) or Django (in the Python world), over something like a more heavyweight J2EE stack. But how your app will scale will depend on a lot more than just your choice of web framework. For many social applications (such as Twitter), the website ends up only being a relatively small part of the overall system, and how the rest of the system is architected becomes very important. Is your app componentized in a way that allows you to scale up individual components as demand increases? Are you going to be able to cache the hell out your system to avoid database access? Etc.</p>

<p>Anyway, good luck with your app!</p>]]></content:encoded>
	</item>
	<item>
		<title>By: zev</title>
		<link>http://www.digitalhobbit.com/2008/05/01/twitter-ruby-on-rails-fud/comment-page-1/#comment-72562</link>
		<dc:creator>zev</dc:creator>
		<pubDate>Sat, 09 Aug 2008 19:40:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.digitalhobbit.com/?p=293#comment-72562</guid>
		<description>&lt;p&gt;We are developing a social application in Ruby on Rails, and we hope that it will scale huge (obviously).&lt;/p&gt;

&lt;p&gt;Would you suggest we do NOT use Ruby on Rails?&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>We are developing a social application in Ruby on Rails, and we hope that it will scale huge (obviously).</p>

<p>Would you suggest we do NOT use Ruby on Rails?</p>]]></content:encoded>
	</item>
</channel>
</rss>
