<p>It infuriates me how miserably inefficient Twitter's design is. It's so un-crisp. Stuff takes forever to load when you click on it-FOREVER-, half the time your clicks don't even register, the pictures don't load about 65% of the time (and it takes a good 8-9 seconds per picture when it is loading 'right'), it's beyond clunky when searching for people (really, no way to search for specific people when looking at someone's followers list or whatever? I'm supposed to go down the list that has to load new names after every 6th person in alphabetical order?), it just...absolutely sucks. I can't imagine a website that is that big and that poorly engineered. </p>
<p>I mean, Facebook has its technical issues with awkward loading and popups when you click stuff, but at least you can mostly do what you want to get done on there. Twitter HAD to have been explicitly designed to have a poor user interface as a social experiment or something. No way that the designers of one of the world's biggest platforms are that comically bad at their jobs.</p>
<ol>
<li><p>I’d recommend that you get off Internet Explorer/whatever crap internet connection you must be paying for, because Twitter’s implementation of Ruby on Rails + Java makes for a much faster website than the aging PHP architecture Facebook employs. If you’re experiencing sluggishness from Twitter, the previously mentioned factors are probably to blame.</p></li>
<li><p>It astounds me that you can’t wrap your head around Twitter’s UI yet claim that Facebook’s UI (a hallmark example of careless UI implementation in design/CS circles) is superior.</p></li>
</ol>
<p>I<code>ve got both, but am not even really ever on Twitter. I think I</code>ve got like maybe 5 tweets…and then I gave up. Kind of dumb. Facebook is better, though 99% at my school would disagree with that.</p>
<p>I shudder every time I see the Masonic Bowl’s website. That right there is a shining example of why it’s wrong for a prestigious event to have such a poor website.</p>