<?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 starting to get de-Railed</title>
	<atom:link href="http://thebull.macsimumweb.com/twitter-starting-to-get-de-railed/feed/" rel="self" type="application/rss+xml" />
	<link>http://thebull.macsimumweb.com/twitter-starting-to-get-de-railed/</link>
	<description>Thoughts on poker, programming and other stuff.</description>
	<pubDate>Sun, 07 Sep 2008 14:35:59 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Cristian Vat</title>
		<link>http://thebull.macsimumweb.com/twitter-starting-to-get-de-railed/#comment-1597</link>
		<dc:creator>Cristian Vat</dc:creator>
		<pubDate>Sat, 09 Jun 2007 15:29:17 +0000</pubDate>
		<guid isPermaLink="false">http://thebull.macsimumweb.com/2007/04/14/twitter-starting-to-get-de-railed/#comment-1597</guid>
		<description>-- Mongrel not being multi-threaded is a real hindrance. --

Sorry to contradict you there but Mongrel is multi-threaded. It's the Rails framework which is not thread-safe and therefore you need to run a cluster of mongrels.
Mongrel is pretty darn fast as far as ruby apps go mostly because the url and header parsing are done in C libraries.
You might want to take a look at merb which is a very stripped down framework when comparing with something like rails but it's thread-safe and can take advantage of mongrel's performance.</description>
		<content:encoded><![CDATA[<p>&#8211; Mongrel not being multi-threaded is a real hindrance. &#8211;</p>
<p>Sorry to contradict you there but Mongrel is multi-threaded. It&#8217;s the Rails framework which is not thread-safe and therefore you need to run a cluster of mongrels.<br />
Mongrel is pretty darn fast as far as ruby apps go mostly because the url and header parsing are done in C libraries.<br />
You might want to take a look at merb which is a very stripped down framework when comparing with something like rails but it&#8217;s thread-safe and can take advantage of mongrel&#8217;s performance.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jamie Quint</title>
		<link>http://thebull.macsimumweb.com/twitter-starting-to-get-de-railed/#comment-1410</link>
		<dc:creator>Jamie Quint</dc:creator>
		<pubDate>Tue, 22 May 2007 19:28:24 +0000</pubDate>
		<guid isPermaLink="false">http://thebull.macsimumweb.com/2007/04/14/twitter-starting-to-get-de-railed/#comment-1410</guid>
		<description>"There are enough people working on Rails directly though, or at least with the various containers, that someone should be on this."

How about someone like Twitter?!

What did Facebook do when memcached didn't meet their needs fully? They built out memcached and everyone benefitted, Twitter should be doing the same thing if multiple DB connections is their problem, I doubt they would have trouble getting a patch noticed.</description>
		<content:encoded><![CDATA[<p>&#8220;There are enough people working on Rails directly though, or at least with the various containers, that someone should be on this.&#8221;</p>
<p>How about someone like Twitter?!</p>
<p>What did Facebook do when memcached didn&#8217;t meet their needs fully? They built out memcached and everyone benefitted, Twitter should be doing the same thing if multiple DB connections is their problem, I doubt they would have trouble getting a patch noticed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: George Bailey</title>
		<link>http://thebull.macsimumweb.com/twitter-starting-to-get-de-railed/#comment-1100</link>
		<dc:creator>George Bailey</dc:creator>
		<pubDate>Sun, 22 Apr 2007 00:01:57 +0000</pubDate>
		<guid isPermaLink="false">http://thebull.macsimumweb.com/2007/04/14/twitter-starting-to-get-de-railed/#comment-1100</guid>
		<description>Another thing we don't know is just how well written Twitter is. It may be reasonable to give the developers the benefit of the doubt, but then let's look at the exposed parts we can see. For instance, wen registering, the full name field is restricted to 20 characters. That right there is a big red flag that the development is not all that thoughtful. *Many* full names don't fit in 20 characters. Surely they could have spared a few more. Even if they had, say,  a hundred million registrants that's not very much disk space.
And the user name is not allowed to have a space in it. There's no good technical reason for that. That's another sign of an "old school" mentality of placing arbitrary restrictions on the users to make it easier on the developers.
Those two things alone make me have to believe there is a lot of room for improvement in the app's code.</description>
		<content:encoded><![CDATA[<p>Another thing we don&#8217;t know is just how well written Twitter is. It may be reasonable to give the developers the benefit of the doubt, but then let&#8217;s look at the exposed parts we can see. For instance, wen registering, the full name field is restricted to 20 characters. That right there is a big red flag that the development is not all that thoughtful. *Many* full names don&#8217;t fit in 20 characters. Surely they could have spared a few more. Even if they had, say,  a hundred million registrants that&#8217;s not very much disk space.<br />
And the user name is not allowed to have a space in it. There&#8217;s no good technical reason for that. That&#8217;s another sign of an &#8220;old school&#8221; mentality of placing arbitrary restrictions on the users to make it easier on the developers.<br />
Those two things alone make me have to believe there is a lot of room for improvement in the app&#8217;s code.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nico</title>
		<link>http://thebull.macsimumweb.com/twitter-starting-to-get-de-railed/#comment-1084</link>
		<dc:creator>Nico</dc:creator>
		<pubDate>Tue, 17 Apr 2007 17:31:37 +0000</pubDate>
		<guid isPermaLink="false">http://thebull.macsimumweb.com/2007/04/14/twitter-starting-to-get-de-railed/#comment-1084</guid>
		<description>If the issue is just about issuing and handling async DB lookups, then Ruby is hardly in trouble -- that's not a language issue (i.e., it's not that Ruby is so dynamic that it can't possibly run effeciently and so there are knees that run performance into the ground).  So, yes, it's a framework issue, and if you'd be willing to write a large and complex application, then you might be willing to write async DB classes; the "it's open source, so you can fix it yourself" attitude seems appropriate in this case, IMO.</description>
		<content:encoded><![CDATA[<p>If the issue is just about issuing and handling async DB lookups, then Ruby is hardly in trouble &#8212; that&#8217;s not a language issue (i.e., it&#8217;s not that Ruby is so dynamic that it can&#8217;t possibly run effeciently and so there are knees that run performance into the ground).  So, yes, it&#8217;s a framework issue, and if you&#8217;d be willing to write a large and complex application, then you might be willing to write async DB classes; the &#8220;it&#8217;s open source, so you can fix it yourself&#8221; attitude seems appropriate in this case, IMO.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dick Davies</title>
		<link>http://thebull.macsimumweb.com/twitter-starting-to-get-de-railed/#comment-1083</link>
		<dc:creator>Dick Davies</dc:creator>
		<pubDate>Tue, 17 Apr 2007 09:23:00 +0000</pubDate>
		<guid isPermaLink="false">http://thebull.macsimumweb.com/2007/04/14/twitter-starting-to-get-de-railed/#comment-1083</guid>
		<description>PHP isn't going to scale any better than Ruby. We're talking about handling multiple users by processes rather than threads - which is exactly how php works (you just have apache children rather than mongrels).

Yes, with j2ee you use threads, but the efficiency of that is very dependant on your JVM/OS - it doesn't magically work better on all platforms. 

I believe that 'caching' in this context means memcached (i.e. DB caching, not application/page caching), which is easy to use with dynamic content (and built into rails).

Whether DHH is a pillock or not shouldn't be part of this discussion. His point that you have the *option* to extend rails easily stands, however.</description>
		<content:encoded><![CDATA[<p>PHP isn&#8217;t going to scale any better than Ruby. We&#8217;re talking about handling multiple users by processes rather than threads - which is exactly how php works (you just have apache children rather than mongrels).</p>
<p>Yes, with j2ee you use threads, but the efficiency of that is very dependant on your JVM/OS - it doesn&#8217;t magically work better on all platforms. </p>
<p>I believe that &#8216;caching&#8217; in this context means memcached (i.e. DB caching, not application/page caching), which is easy to use with dynamic content (and built into rails).</p>
<p>Whether DHH is a pillock or not shouldn&#8217;t be part of this discussion. His point that you have the *option* to extend rails easily stands, however.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Erick</title>
		<link>http://thebull.macsimumweb.com/twitter-starting-to-get-de-railed/#comment-1081</link>
		<dc:creator>Erick</dc:creator>
		<pubDate>Mon, 16 Apr 2007 20:47:47 +0000</pubDate>
		<guid isPermaLink="false">http://thebull.macsimumweb.com/2007/04/14/twitter-starting-to-get-de-railed/#comment-1081</guid>
		<description>I'm in the process of going through a redesign for the web community I'm in charge of.  We've been looking at Ruby.  This whole discussion makes me think staying with PHP is the right way to go for now.</description>
		<content:encoded><![CDATA[<p>I&#8217;m in the process of going through a redesign for the web community I&#8217;m in charge of.  We&#8217;ve been looking at Ruby.  This whole discussion makes me think staying with PHP is the right way to go for now.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Bull</title>
		<link>http://thebull.macsimumweb.com/twitter-starting-to-get-de-railed/#comment-1074</link>
		<dc:creator>The Bull</dc:creator>
		<pubDate>Mon, 16 Apr 2007 03:06:46 +0000</pubDate>
		<guid isPermaLink="false">http://thebull.macsimumweb.com/2007/04/14/twitter-starting-to-get-de-railed/#comment-1074</guid>
		<description>Ismael: No, he may not personally owe anybody anything. There are enough people working on Rails directly though, or at least with the various containers, that someone should be on this.

No everyone has the resources to contribute back. Besides, it can take quite a while to actually figure out how a framework really works. In this case it probably isn't so much the Rails framework itself, but the container(s). 

As for vendors, don't even get me started there. They are the worst with support and they won't come running to fix your problems. They will give the same excuses that everyone else does "oh just throw some more hardware at it"</description>
		<content:encoded><![CDATA[<p>Ismael: No, he may not personally owe anybody anything. There are enough people working on Rails directly though, or at least with the various containers, that someone should be on this.</p>
<p>No everyone has the resources to contribute back. Besides, it can take quite a while to actually figure out how a framework really works. In this case it probably isn&#8217;t so much the Rails framework itself, but the container(s). </p>
<p>As for vendors, don&#8217;t even get me started there. They are the worst with support and they won&#8217;t come running to fix your problems. They will give the same excuses that everyone else does &#8220;oh just throw some more hardware at it&#8221;</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://thebull.macsimumweb.com/twitter-starting-to-get-de-railed/#comment-1073</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:24:59 +0000</pubDate>
		<guid isPermaLink="false">http://thebull.macsimumweb.com/2007/04/14/twitter-starting-to-get-de-railed/#comment-1073</guid>
		<description>[...] Until someone goes and pushes the boundary way beyond those who&#8217;ve come before. Suddenly, the gorilla has grabbed your girl, climbed to the top of the Empire State and is angrily swatting light aircraft left, right and centre. [...]</description>
		<content:encoded><![CDATA[<p>[...] Until someone goes and pushes the boundary way beyond those who&#8217;ve come before. Suddenly, the gorilla has grabbed your girl, climbed to the top of the Empire State and is angrily swatting light aircraft left, right and centre. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ismael</title>
		<link>http://thebull.macsimumweb.com/twitter-starting-to-get-de-railed/#comment-1072</link>
		<dc:creator>Ismael</dc:creator>
		<pubDate>Sun, 15 Apr 2007 20:55:04 +0000</pubDate>
		<guid isPermaLink="false">http://thebull.macsimumweb.com/2007/04/14/twitter-starting-to-get-de-railed/#comment-1072</guid>
		<description>Dude, he (DHH) wrote Rails for you to use, for free!. Do you think he ows you fixing your particular problems? He also runs a business, he´s also busy improving other aspects of the framework. This is the sort of reasons Twitter chose to go with an Open Source framework in the first place, as opposed to a propietary solution where the vendor will, indeed, run to fix your problems in exchange for juicy bucks. You have a scalability issue with Rails? Fix it. Write a plugin or something. Share it. DHH did it with an entire framework, and he didn't really had to.</description>
		<content:encoded><![CDATA[<p>Dude, he (DHH) wrote Rails for you to use, for free!. Do you think he ows you fixing your particular problems? He also runs a business, he´s also busy improving other aspects of the framework. This is the sort of reasons Twitter chose to go with an Open Source framework in the first place, as opposed to a propietary solution where the vendor will, indeed, run to fix your problems in exchange for juicy bucks. You have a scalability issue with Rails? Fix it. Write a plugin or something. Share it. DHH did it with an entire framework, and he didn&#8217;t really had to.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Balance On Rails</title>
		<link>http://thebull.macsimumweb.com/twitter-starting-to-get-de-railed/#comment-1071</link>
		<dc:creator>Balance On Rails</dc:creator>
		<pubDate>Sun, 15 Apr 2007 20:30:57 +0000</pubDate>
		<guid isPermaLink="false">http://thebull.macsimumweb.com/2007/04/14/twitter-starting-to-get-de-railed/#comment-1071</guid>
		<description>[...] Twitter starting to get de-Railed » Thinking Outloud    Apr 14 [...]</description>
		<content:encoded><![CDATA[<p>[...] Twitter starting to get de-Railed » Thinking Outloud    Apr 14 [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
