<?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: Rails woes. The slow that is keeping twitter down.</title>
	<atom:link href="http://www.nata2.org/2007/04/15/rails-woes-the-slow-that-is-keeping-twitter-down/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.nata2.org/2007/04/15/rails-woes-the-slow-that-is-keeping-twitter-down/</link>
	<description>Harper Reed: Software, PHP, MySQL, YoYo, Juggling, Baphomet</description>
	<pubDate>Fri, 29 Aug 2008 00:10:51 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7-hemorrhage</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: mormon</title>
		<link>http://www.nata2.org/2007/04/15/rails-woes-the-slow-that-is-keeping-twitter-down/#comment-84508</link>
		<dc:creator>mormon</dc:creator>
		<pubDate>Mon, 11 Aug 2008 22:37:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.nata2.org/2007/04/15/rails-woes-the-slow-that-is-keeping-twitter-down/#comment-84508</guid>
		<description>I agree that rails is slow.  It really is.  I think Ruby itself might even be fast, but somehow rails manages to slow it right down.  Or maybe it is Ruby, I'm not sure. 

Also I really agree with the quote that rails is good but "if you get big enough rails will suffer."  It will indeed.  Thankfully, however most e-commerce sites don't get slammed, so rails actually honestly is fast enough for them.  Though I suppose it's a little disconcerting what you noted about php being faster so getting more clicks.  Wonder if it's the prototype .js's or something.  Just my $0.02</description>
		<content:encoded><![CDATA[<p>I agree that rails is slow.  It really is.  I think Ruby itself might even be fast, but somehow rails manages to slow it right down.  Or maybe it is Ruby, I&#8217;m not sure. </p>
<p>Also I really agree with the quote that rails is good but &#8220;if you get big enough rails will suffer.&#8221;  It will indeed.  Thankfully, however most e-commerce sites don&#8217;t get slammed, so rails actually honestly is fast enough for them.  Though I suppose it&#8217;s a little disconcerting what you noted about php being faster so getting more clicks.  Wonder if it&#8217;s the prototype .js&#8217;s or something.  Just my $0.02</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Twitter Slowing WAY Down</title>
		<link>http://www.nata2.org/2007/04/15/rails-woes-the-slow-that-is-keeping-twitter-down/#comment-78112</link>
		<dc:creator>Twitter Slowing WAY Down</dc:creator>
		<pubDate>Wed, 21 May 2008 21:43:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.nata2.org/2007/04/15/rails-woes-the-slow-that-is-keeping-twitter-down/#comment-78112</guid>
		<description>[...] Ruby on Rails be damned! [...]</description>
		<content:encoded><![CDATA[<p>[...] Ruby on Rails be damned! [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sumit Khanna</title>
		<link>http://www.nata2.org/2007/04/15/rails-woes-the-slow-that-is-keeping-twitter-down/#comment-74349</link>
		<dc:creator>Sumit Khanna</dc:creator>
		<pubDate>Mon, 21 Apr 2008 20:55:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.nata2.org/2007/04/15/rails-woes-the-slow-that-is-keeping-twitter-down/#comment-74349</guid>
		<description>I have to agree quite a bit. I have a love hate relationship with Ruby on Rails too. It seems really nice and does a lot of stuff for you, but it is slow compared to my PHP apps, even apps built on bulky frameworks like Drupel. 

I'm going back to PHP for new development, but I'm taking a lot of the concepts I learned from Rails (as well as some J2EE concepts) and making my own little / simple framework that is more tailored to what I need it to do. 

Ruby on Rails is a nice box and a good environment to try to force programmers to write good MVC code, but try to build outside that framework, or interface with non-ruby databases and you get a lot of issues.

Also, I rather write my own SQL that use Active Record. I like writing SQL and looking through the logs, I always feel I could write better SQL than what they auto-generate. 

PHP has been out much longer and there is so much stuff out there for it that still works in PHP5 even though it was intended for 4. Rails is poorly documented, the same stuff in Rails 1 doesn't work in Rails 2 and the community feels as arrogant as the Debian junkies. 

-Sum</description>
		<content:encoded><![CDATA[<p>I have to agree quite a bit. I have a love hate relationship with Ruby on Rails too. It seems really nice and does a lot of stuff for you, but it is slow compared to my PHP apps, even apps built on bulky frameworks like Drupel. </p>
<p>I&#8217;m going back to PHP for new development, but I&#8217;m taking a lot of the concepts I learned from Rails (as well as some J2EE concepts) and making my own little / simple framework that is more tailored to what I need it to do. </p>
<p>Ruby on Rails is a nice box and a good environment to try to force programmers to write good MVC code, but try to build outside that framework, or interface with non-ruby databases and you get a lot of issues.</p>
<p>Also, I rather write my own SQL that use Active Record. I like writing SQL and looking through the logs, I always feel I could write better SQL than what they auto-generate. </p>
<p>PHP has been out much longer and there is so much stuff out there for it that still works in PHP5 even though it was intended for 4. Rails is poorly documented, the same stuff in Rails 1 doesn&#8217;t work in Rails 2 and the community feels as arrogant as the Debian junkies. </p>
<p>-Sum</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rails and Wired magazine &#187; Harper Reed: Tech, Phones, Yo-yoing and Death Metal</title>
		<link>http://www.nata2.org/2007/04/15/rails-woes-the-slow-that-is-keeping-twitter-down/#comment-66371</link>
		<dc:creator>Rails and Wired magazine &#187; Harper Reed: Tech, Phones, Yo-yoing and Death Metal</dc:creator>
		<pubDate>Sat, 23 Feb 2008 21:54:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.nata2.org/2007/04/15/rails-woes-the-slow-that-is-keeping-twitter-down/#comment-66371</guid>
		<description>[...] I have blogged about this before. [...]</description>
		<content:encoded><![CDATA[<p>[...] I have blogged about this before. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ¿Ruby on Rails está muerto? &#124; jRuby</title>
		<link>http://www.nata2.org/2007/04/15/rails-woes-the-slow-that-is-keeping-twitter-down/#comment-38829</link>
		<dc:creator>¿Ruby on Rails está muerto? &#124; jRuby</dc:creator>
		<pubDate>Thu, 25 Oct 2007 16:27:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.nata2.org/2007/04/15/rails-woes-the-slow-that-is-keeping-twitter-down/#comment-38829</guid>
		<description>[...] RoR hace lento a Twitter [...]</description>
		<content:encoded><![CDATA[<p>[...] RoR hace lento a Twitter [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lenguajes de desarrollo web &#171; Cosas sencillas</title>
		<link>http://www.nata2.org/2007/04/15/rails-woes-the-slow-that-is-keeping-twitter-down/#comment-24116</link>
		<dc:creator>Lenguajes de desarrollo web &#171; Cosas sencillas</dc:creator>
		<pubDate>Wed, 06 Jun 2007 06:40:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.nata2.org/2007/04/15/rails-woes-the-slow-that-is-keeping-twitter-down/#comment-24116</guid>
		<description>[...] y evitar que se repita código innecesariamente. Sin embargo, este programa ha presentado problemas de escalabilidad (es decir, capacidad para responder a una creciente demanda de usuarios) en sitios de gran éxito [...]</description>
		<content:encoded><![CDATA[<p>[...] y evitar que se repita código innecesariamente. Sin embargo, este programa ha presentado problemas de escalabilidad (es decir, capacidad para responder a una creciente demanda de usuarios) en sitios de gran éxito [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy</title>
		<link>http://www.nata2.org/2007/04/15/rails-woes-the-slow-that-is-keeping-twitter-down/#comment-21390</link>
		<dc:creator>Andy</dc:creator>
		<pubDate>Fri, 04 May 2007 00:00:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.nata2.org/2007/04/15/rails-woes-the-slow-that-is-keeping-twitter-down/#comment-21390</guid>
		<description>If you are big on the MVC design pattern and know PHP, why not give Code Igniter a shot? www.codeigniter.com  I have used it on a couple of projects and am REALLY pleased so far.  It is fairly new, but the community is epic.  Lots of new development and great support/feedback.  It has active record, and other goodies that Rails has.</description>
		<content:encoded><![CDATA[<p>If you are big on the MVC design pattern and know PHP, why not give Code Igniter a shot? <a href="http://www.codeigniter.com" rel="nofollow">http://www.codeigniter.com</a>  I have used it on a couple of projects and am REALLY pleased so far.  It is fairly new, but the community is epic.  Lots of new development and great support/feedback.  It has active record, and other goodies that Rails has.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: What I accidently learnt about programming &#187; Open source Scaling Ruby vs PHP</title>
		<link>http://www.nata2.org/2007/04/15/rails-woes-the-slow-that-is-keeping-twitter-down/#comment-19857</link>
		<dc:creator>What I accidently learnt about programming &#187; Open source Scaling Ruby vs PHP</dc:creator>
		<pubDate>Thu, 19 Apr 2007 08:17:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.nata2.org/2007/04/15/rails-woes-the-slow-that-is-keeping-twitter-down/#comment-19857</guid>
		<description>[...] Harper Reed [...]</description>
		<content:encoded><![CDATA[<p>[...] Harper Reed [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: &#187; Ruby y la burbuja deUgarte.com</title>
		<link>http://www.nata2.org/2007/04/15/rails-woes-the-slow-that-is-keeping-twitter-down/#comment-19807</link>
		<dc:creator>&#187; Ruby y la burbuja deUgarte.com</dc:creator>
		<pubDate>Wed, 18 Apr 2007 19:52:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.nata2.org/2007/04/15/rails-woes-the-slow-that-is-keeping-twitter-down/#comment-19807</guid>
		<description>[...] aplicaciones web fuertes con Ruby on Rails tiene sus problemas. Mucho est?n sonando estos d?as los que sufre twitter y parece que hay un cierto consenso sobre los l?mites de la escalabilidad que bajo ciertos [...]</description>
		<content:encoded><![CDATA[<p>[...] aplicaciones web fuertes con Ruby on Rails tiene sus problemas. Mucho est?n sonando estos d?as los que sufre twitter y parece que hay un cierto consenso sobre los l?mites de la escalabilidad que bajo ciertos [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mh</title>
		<link>http://www.nata2.org/2007/04/15/rails-woes-the-slow-that-is-keeping-twitter-down/#comment-19649</link>
		<dc:creator>mh</dc:creator>
		<pubDate>Mon, 16 Apr 2007 22:41:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.nata2.org/2007/04/15/rails-woes-the-slow-that-is-keeping-twitter-down/#comment-19649</guid>
		<description>I love the suggestion halfway through the DHH post where he implies that this would be a great opportunity for the twitter people to contribute, like it's your RESPONSIBILITY to contribute to the community when you encounter a scaling problem. This is basically the nightmare that every corporation throws out whenever someone recommends open source solutions that leads people to stick with large vendors. Not that large vendors are responsive either, but there's that mythical culpability.

Ideally a company that is enthusiastic about the technology meets the framework developers halfway, but is it wrong for me to think that you should be able to wholeheartedly use and endorse a technology without taking on its development when there are others out there?</description>
		<content:encoded><![CDATA[<p>I love the suggestion halfway through the DHH post where he implies that this would be a great opportunity for the twitter people to contribute, like it&#8217;s your RESPONSIBILITY to contribute to the community when you encounter a scaling problem. This is basically the nightmare that every corporation throws out whenever someone recommends open source solutions that leads people to stick with large vendors. Not that large vendors are responsive either, but there&#8217;s that mythical culpability.</p>
<p>Ideally a company that is enthusiastic about the technology meets the framework developers halfway, but is it wrong for me to think that you should be able to wholeheartedly use and endorse a technology without taking on its development when there are others out there?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
