<?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"
	>
<channel>
	<title>Comments on: Twitter / Ruby on Rails FUD</title>
	<atom:link href="http://www.digitalhobbit.com/archives/2008/05/01/twitter-ruby-on-rails-fud/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.digitalhobbit.com/archives/2008/05/01/twitter-ruby-on-rails-fud/</link>
	<description>Thoughts from the hobbit hole</description>
	<pubDate>Sat, 22 Nov 2008 20:21:44 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: DigitalHobbit</title>
		<link>http://www.digitalhobbit.com/archives/2008/05/01/twitter-ruby-on-rails-fud/#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>Hi Zev,

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.

Anyway, good luck with your app!</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/archives/2008/05/01/twitter-ruby-on-rails-fud/#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>We are developing a social application in Ruby on Rails, and we hope that it will scale huge (obviously).

Would you suggest we do NOT use Ruby on Rails?</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>
