a statement
I just want to go on record saying that none of Twitter's problems have ever been Rails problems.
postscript
Brandon Keene is right on.
July 10, 2008
6 comments
In that same vein, Rails has little to do with Twitter's success.
I guess Rails is irrelevant then.
I second Dobbs.
I am damn sure, Rails definitely helped them to build such a nice site.
I think that Rails contributed to Twitter's *existence* rather than success. I know lots of people who could finally get their projects off the ground because they could develop them quicker. Having something to show someone in short order can go a long way towards someone giving you more money to expand.
I'm certain that Twitter would have been successful even without Rails, I suspect that if it had been done in PHP it would have taken longer. I do know that some sites use Rails to build the first version and reimplement in something else when they get more money. It's certainly a great way to quickly find out if you have a good or profitable idea on your hands.
Just my .02. I can do something in 20 hours now that used to take me 200 because I don't fight with the language or the platform.


The Devil says (July 10, 2008):
Or do they have EVERYTHING to do with rails?