We routinely run 5MM simultaneous TCP/IP connections on a single 12-core box (with Erlang!).
There's no reason for Twitter to need all those employees and all that hardware. If someone can get it at a fire sale price, and reduce it to 100 employees, they can have a nice business.
As a point of reference, even the Wikimedia Foundation had almost 300 staff and contractors as of 2015. This is admittedly a lot fewer than Twitter employs today. However, I suspect that even a minimalist Twitter without sales, etc. needs more employees and would have more of other types of costs than Wikimedia.
> As a point of reference, even the Wikimedia Foundation had almost 300 staff and contractors as of 2015. This is admittedly a lot fewer than Twitter employs today.
Exactly, that's actually a pretty good argument for why Twitter should downsize substantially.
In no way does Twitter need more than 1,000 employees.
And frankly, much of the same criticism applies to them. A tiny tiny sliver of their constantly multiplying budget is spent on actually hosting the Wikipedia.
That's somewhat fair. It's certainly true that Wikimedia has a fair number of active projects that haven't had much of an impact. Apparently there have been at least some discussions of streamlining their work although organizations universally find it hard to avoid scope creep.
I'd point out though that, according to Wikipedia :-), the Internet Archive has a staff of about 200 so a few hundred employees/contractors doesn't seem out out of line as the baseline for a non-profit information infrastructure project.
If Twitter only needed to serve the states, sure. But they need to sync servers globally and provide decent bandwidth to every corner of the developed world. That's a big $ technical problem.
There's no reason for Twitter to need all those employees and all that hardware. If someone can get it at a fire sale price, and reduce it to 100 employees, they can have a nice business.