I’m not surprised to see Twitter’s reliability get progressively worse. Overall, I think they could have reduced engineering staff in the long term by adopting mainstream open source technologies instead of their own custom (albeit also oss) database/filesystem/streaming system/rpc library/spark stack. But those migrations would have taken years. Instead, slashing staff that fast is likely to cause slow rot of their…
You think Twitter / X is bad for reliability, then you haven't seen the frequency of GitHub outages for over 100M+ users for over 3 years and this is with having Microsoft's backing. Yet somehow GitHub's outages are tolerated with something breaking over there every week. I have not seen anything else break more times than GitHub even having Microsoft footing the bill and they should have a much higher uptime than Tw…
This isn't exactly a hard concept to grasp though: it's entirely possible to use GitHub and still be productive when it's temporarily offline; Git doesn't stop working on your local machine because GitHub is down.
It's literally impossible to use Twitter when it's temporarily offline. There is no "offline" mode for Twitter.
There is also the argument to be made that (a) what GitHub does is orders of magnitude more complex than what Twitter does, and (b) I don't recall anyone buying a controlling stake in GitHub and then loudly declaring that it doesn't need all those staff and firing (IIRC) all but one of the Ops team.