I guess I personally wouldn't categorize it as a "mess" and the conversations I read about it here make me think I'm using an entirely different product than everyone else.
I guess I personally wouldn't categorize it as a "mess" and the conversations I read about it here make me think I'm using an entirely different product than everyone else.
I use it quite a lot and the first time I actually witnessed downtime myself was yesterday.
github for large project that rely on CI tool is a nightmare (cost, downtime, etc.)
I'm guessing you dont know about the github actions bug that was running and endless loop consuming 100% cpu costing orgs insane amounts of money that they didn't fix for 3 years.
It also shows there’s a fundamental problem with their architecture or their development pattern to have these sorts of issues so frequently.
Migrating to different cloud vendors, while difficult, is something that people have done many times before. There's only finite number of incongruences that appear when moving cloud vendors. It's rather difficult to explain the ongoing problems several years after the fact.
Anyone that's worked at a startup knows that one of the best things about it is reflecting on all of the asinine, if not genuinely stupid policies of your previous employer so as not to repeat them. Without any insider knowledge, the practices and procedures GitHub had prior to acquisition probably look nothing like those post-acquisition.
Anecdotally: at work I saw quite a lot of github-uptime-related issues, and because they're the central host for everything they become *cough* load bearing for a huge amount of the company. Stability and performance has been dramatically worse than the self-hosted phabricator+gitolite before it.
Earlier today our app, used by a handful of actual production customers, went down for 30 minutes due to a GCP migration to a new project and we screwed up a secret in prod. This was an all hands on deck firedrill with 5 whys and incident reports and chaos.
Github has been having major production outages routinely! There are companies who can't release, can't build, can't view issues, basically can't work. I'd imagine most orgs using Github have been forced to move off of them or create an alternate approach to actually get shit done.
I use GitHub a lot and it does what I need well enough, but I wouldn't spend money on the level of service or performance it generally delivers.