For the past three weeks or so, the wonderous twitter has been completely hosed for me. Behold the beautiful 500 message I get each and every time I hit the home link.
I’ve emailed them about this, and heard screw all back. Friends of mine have been complaining about a myriad of issues while using twitter as well. I get it, they have tons of traffic. What I don’t get is why they haven’t fixed the site yet. Perhaps they’re spending all their support cycles on a potential PHP rewrite.
The developers in twitter land have complained ad infinitum about how shitty rails is with scaling, but I’m wondering if the fact that this was their first rails site has anything to do with it.
As far as I’m concerned, twitter is for the birds. Pun totally intended.
The TechCrunch article about switching from Rails ended up being, well, completely wrong. The problem really isn’t about Rails or Ruby; it’s more about Twitter not being a traditional web app. It doesn’t really scale comparatively. I don’t think a switch to PHP or any other traditional web-focused language would really solve anything at this point.
They don't use much Rails at all... and the rewrite rumors are all false... but I do agree, they need to get their act together fast...
Where else are you going to go for your quick status needs? HAHA I said needs...
@Jake
> Where else are you going to go for your quick status needs?
Honestly, the site just tanks for me anyway, so I'm essentially forced to go somewhere else regardless.