"Martin, I assume you are complimenting Alex on the nice work of Twitter. I know Alex was deeply involved in the new API released this week including the potential difficulties (and advantages) of using Google Docs."

"This is a great look behind the scenes of Twitter, especially for all of the Rubyists out there."

"This is truly the most informative piece of blogging on Twitter that I?ve seen to date. I?ve written some how-to stuff, and some social neato stuff, but wow. This was really interesting. A true peak under the kitty cats. Thanks!"

"think blogging is a replacement for journalism.? Kinda sums it all up! Thanks for the interview."

"[?] had started writing a Twitter mash-up in Ruby on Rails, but then after my interview with Alex Payne and some tests our IT guys ran in our hosting environment, I was convinced that Ruby is hard to [?]"

"[?] However, its always good to stay informed and know about the issues other developers are facing. Read the whole interview via radicalbehavior Posted by strong Filed in Uncategorized April 11th, [?]"

"[?] the desk of Alex Payne: All of us working on Twitter are big Ruby fans, but I think it?s worth being frank that this [?]"

"If you?re looking for all of the dynamic-language, rapid-development pleasure of Rails, plus *much* better performance, give Django a shot: djangoproject.com."

"[?] I was fairly convinced that it would make serious scaling a huge pain in the butt. Today, by way of an interview of a Twitter developer, comes the answer I?ve been expecting: Running on Rails has forced us to deal with scaling [?]"

"[?] negative comments about Rails, you instantly get attacked online, right? True, unless you?re a developer for Twitter. Look, I love Rails, I really do, it?s a great framework, it?s fun to use, it?s [?]"

"I don?t think the term ?syntactical sugar? is what you wanted to use, since the connotation of ?syntactical sugar? typically infers not only that the syntax makes it a little easier to do something, but also that the syntax change doesn?t have a performance penalty. Unless you are referring to what others have called ?syntactical sugar? and your point is that it isn?t really ?syntactical sugar?."

"[?] Interesting interview with one of Twitter?s developers (see previous post about microblogging). I?ve been wondering how Ruby on Rails scales, i guess this answers that. [?]"

"[?] gave a phenomenal interview on Twitter and Rails a couple of weeks ago. This morning its all over the Net ? but folks I think are taking the [?]"

"Maybe I can start pointing to this interview to get the Ruby on Rails community to stop trying to force Rails down our throats?"

"[?] the Blogger Meetup folks that stop through here, I just ran across this article about Alex. I had no idea he joined the Twitter team. Anywho, good luck to [?]"

"[?] 5 Question Interview with Twitter Developer Alex Payne ?ll the convenience methods and syntactical sugar that makes Rails such a pleasure for coders ends up being absolutely punishing, performance-wise? Ruby is slow.? (tags: ruby twitter rails performance scaling) Posted by jermolene Filed in Uncategorized [?]"

"[?] einem Interview mit Josh Kenzer lässt Alex Payne,einer der Twitter Developer tief in die Karten der derzeit größen auf Ruby on Rails [?]"

"[?] an interview with one of the developers on the twitter.com team: I think the real power of Twitter is its [?]"

"I still don?t know exactly what ?Ruby on Rails? is? Some guy tried to sell me some last night, said it would get me ?high as a mother fucker?. I?m not wearing pants."

"[?] WebApp Skalierungsprobleme mit sich bringt ist klar. Einer der beteiligten Entwickler bringt in einem Interview durchaus etwas Frust zum Ausdruck: Running on Rails has forced us to deal with scaling issues - [?]"

"Its interesting to hear someone talk about a language that is slow and not talk about how to better do it in a faster language. I am talking about php/python. Would Twitter be better off running on a more ?mainstream? system? Just a thought - don?t kill me "

"I?m not entirely buying the Ruby speed argument. Sure, we know Ruby is slower than other languages, but when dealing with the Web, databases, etc, it really doesn?t matter unless you need to do some serious "

"Put it this way, I?ve taken some reasonably well performing Perl daemon code I have that serves hundreds of millons of requests per month, and managed to port it to Ruby and make it even faster.. so I?m just not buying that Ruby?s performance is really an issue with Web applications."

"So what is the argument then for a language? Comfort? Given that the speed of web apps is neg-lable, one should program in any language they choose? I started out in perl and understand that perl can be 100% awesome vs a PHP hack or something. How about the (sorry) fastCGI issue? doesn?t that hinder the performance of the web app? I am sorry to just call that out but if it is an issue then I must. This is not a disagreement but a debate, please contribute to it, anyone "

"My personal opinion is that languages can win and lose on factors like the quality of libraries, quality of deployment systems (case in point, mod_php vs everything else), ability of the language to interface with other things, qualit of frameworks, etc. Those things are related to the ecosystem of a language rather than the core performance of the language per-se."

"[?] Kenzer has posted an interview with Alex Payne, a developer for Twitter, which is one of (if not the) biggest Ruby on Rails-based web apps. A [?]"

"I just soft-launched my rails-based video tracker and I am using the caching all over the place. It is easy to do and every rails developer should put it in before launching."

"The language is amazingly cool to develop in, and rails saves a lot of time even if the data modelling approach is somewhat simplistic. But I can definitely see a performance difference between ruby and languages such as perl, php, and even java."

"As with everything in engineering, you have to deal with difficult trade-offs. With Memecat, I chose to pay for coding happiness with more processor heat and server memory."

"[?] placing the blame squarly on the Ruby on Rails framework.  Alex explains in an interview with Josh Kezner, It?s also worth mentioning that there shouldn?t be doubt in anybody?s mind at [?]"

"[?] researching it recently. This post on DHH?s blog informed me of that. The entry references an interview with a Twitter developer about their scaling issues. By various metrics Twitter is the biggest [?]"

"[?] 5 Question Interview with Twitter Developer Alex Payne ?Itâ??s also worth mentioning that there shouldnâ??t be doubt in anybodyâ??s mind at this point that Ruby itself is slow. Itâ??s great that people are hard at work on faster implementations of the language, but right now, itâ??s tough.? (tags: via:Ted Ruby performance dynamiclanguages Twitter Rails) [?]"

"[?] had 6,160 visitors to my blog?yesterday! Most the traffic is to read the interview with Twitter developer Alex Payne. The second most popular is the post about experimenting with [?]"

"[?] little tempest in a teapot the past day or so has been the interview Twitter developer, Alex Payne did. In it, he somewhat calls out Rails for some of the performance [?]"

"[?] Twitter is apparently the busiest Rails site on the net, and here is what they have to say about it: 2. How has Ruby on Rails been holding up to the increased load? By various metrics [?]"

"[?] one of the Twitter developers, whose app is peaking 11,000 requests per second at the [?]"

"[?] tema viene del artĂ­culo y debate Twitter Problem, surgido a raĂ­z de una entrevista a Alex Payne, uno de los desarrolladores de Twitter. Me llamĂł muchĂ­simo la [?]"

"[?] 5 Question Interview with Twitter Developer Alex Payne I came to Rails after working in PHP like many developers, but Iâ??ve never been a language purist. (tags: "

"[?] 5 Question Interview with Twitter Developer Alex Payne The developer of Twitter talks scaling. (tags: twitter startups) [?]"

"@Adrian Holovaty: Dude, this is so lame. Is this all you guys can do? look for disaffected companies and try to pitch your framework? almost like ambulance chasing.."

"@Peter: Dear Pete, Ruby is slow, it eats CPU for breakfast, and please show us your million hits per month code. I?m sure its proprietary and you can?t show it to us."

"Rails is braindamaged when it comes to scaling. Reason? It was developed by an MIS/Marketing student with delusions of programming grandeur. DHH doesn?t know his RDBMS from his buttocks! And that?s the godawful truth."

"And now he?s squirming like a little you know who, because the rubber is hitting the road, and the thing doesn?t scale on the DB end. Well, this is what you get when you don?t understand the issues involved, and bitchslap anyone who brings them up in the initial phases in the name of ?opinionation?."

"Don?t know what will come, maybe it will be an Erlang framework (No Thanks ErlyWeb, you?re just as ugly as rails, but we can be hi-bye friends..) or seaside or whatever.. but something is going to really cut rails and all its hype down a few notches (despite all the efforts of the blogocircuit talking heads milking the hell out of php-converts)"

"No Wonder PragProg is offering an Erlang book to seed a ?new wave? of ?pragmatic? cash-cow-milking, but hey, you can never blame an entrepreneur.. especially a pragmatic one."

"Al3x, I hope DHH and 37S don?t get you fired from this, because what you?re dealing with is a sleazy marketing machine wrapping itself up in the post-rape sheets of opensource. They don?t like it when people mess with their revenue streams and their little conference-filling cash cow called ?Ruby on Rails?"

"[?] to this interview with a developer at Twitter, that site is currently the largest Ruby on Rails site in operation [?]"

"JustAnOutside: It?s not all proprietary, but I don?t need to show it either. Just rig up a basic script that uses Mongrel (at library level) and returns stuff cached in Memcached, and you?ll easily hit 700m~1bn requests per month on a single box. It takes half an hour to run up such a test. Ruby is almost irrelevant in this example as the amount of processing to send stuff to HTTP clients is minimal."

"Then it all comes down to what percentage of requests have to hit a database or do some sort of logic, but as long as it?s under a certain percentage, you?re good."

"Note, I?m not talking about Rails.. which is slow. I?m talking about actually developing your own stuff with Ruby. My argument is that Ruby?s speed is nearly irrelevant when it comes to fielding data between databases and networks.. since databases and networks are always slower than Ruby! (but not Rails)"

"[?] Software at 11:21 am by mj It?s been a fun week. Two weeks ago, Twitter developer Alex Payne gave a short interview, in which he talked about Twitter?s scaling issues. The money quote: Running on Rails has [?]"

"@PeterCooper: Agreed. Ruby?s speed is almost irrelevant, though it does affect the overall performance of an app especially through a framework which adds layers of abstraction (for developer productivity no doubt but still)."

"My general point is that Rails was not developed with performance in mind, which is very typical of run-of-the-mill developers, DHH being no exception. He created something which made sense to him and his rather superficial understanding of the performance issues and that is just as well. But let us not forget that DHH?s major problem while creating BASECAMP was _NOT_ performance and scaling, but Time to Market, and rails did that beautifully _for them_ It doesn?t mean DHH or rails community should start pretending it will work in all situations because Rails is beauty this and joy that and it just fits their brains and all that new-agey non-sense that DHH tries to spread all the time."

"My issue is with 37S and gang protecting RoR as a corporate brand without stating it in so many words, and attacking even their most valued customers (RoR users are the other side of the Brand coin) who are in reality helping to test the framework to its limits."

"They are not going to get far with this type of attitude attacking someone and accusing them of being lazy if the users dare to point out some deficiencies in the framework which are well known in the community to begin with."

"DHH hints that multi-database solutions are possible with rails without offering so much as a link. If they are and a team running an 11k hps site doesn?t know it, then they should all
... read the whole article