Twitter: Something is technically wrong
Step 1) Have great idea. Step 2) ????. Step 3) Profit! Apparently someone didn’t tell Twitter that Step 2 is “don’t fuck it up“. Twitter’s lack of stability and massive downtime lately has been pretty horrid. Rumors that they’ve gotten another 15M in funding are swirling around, but also rumors of technical incompetence there abound. Unlike somewhere such as 37Signals (or betahouse) they don’t have programming rockstars working for them it seems.
Yes, twitter has unique problems. They will require unique solutions. Until someone figures them out however, I think I’m going to back off using/caring about twitter. This is really sad. In the past year I’ve learned to love twitter. Yet, nonstop slowdowns, client bugs, downtime, etc have kinda killed it for me.
Maybe their goal and monetization plan is to get everyone hooked, claim that they can’t keep it up without charging for it, and then get everyone to pay since they are addicted like Crack. I think they’ll hop to Pownce instead. Speaking of, why doesn’t Pownce have similar problems?
Maybe they need to write the program in pure Ruby, or maybe they need to use a “faster” language like Java or C++ to write it. The rails community will surely cry if it comes to this, but it will likely be needed.
But either way, someone wake me up when Twitter has some degree of stability. Until then, I think I’ll just have to be out of the loop.


Comments(1)
