4 comments

It’s bad engineering done by kids with no experience trying to cram 2 new features into code that already consumes 511 of the available 512 bytes of code in a 68HC11. Or at least that’s what this crotchety old programmer thinks.

The last time I did the math, twitter had an aggregate flow rate somewhere around 60k / second. Let’s presume growth, and say it’s now 100k/second. I’ve got a stack of old PCs in my office, and I’d be willing to bet cold hard cash that I could take 10 of them, and make them into a cluster capable of handling the full tweet load.

Twitter is the Chicago Cubs of networking services. It’ll be better, just wait until next year! 8)