Comment by margalabargala
20 hours ago
I'm glad you are optimistic. GitHub will need employees with that attitude if they're going to pull out of their current trajectory.
To be clear- from a user perspective, "improving GitHub" means "restoring reliability to what it was 6 years ago". There's no killer feature that makes people stop leaving, if my PRs don't lead every third day and actions never work.
I may have my timelines wrong but I don't remember github being rock solid 5 years ago. I remember multiple outages keeping us from pulling code for go packages that were not using an enterprise dependency cache and killing multiple days of work a year for those systems. It's what I used as a forcing function to move people TO an enterprise dependency cache, and to find the few scofflaws running work code off of github.com versus enterprise.
You're right. I was misremembering this graph:
https://damrnelson.github.io/github-historical-uptime/
Actually to me the answer is Ms made them get more accurate in their graph. It was definitely not Rick solid in 2015-2018
https://techcrunch.com/2017/07/31/github-goes-down-and-takes...
Another line on that graph should probably be "January 7, 2019: GitHub offers unlimited free private repos". I can't imagine that helps with service stability.
That is a pretty wild graph
7 replies →
Security: No leaking PII, no compromised build pipelines.
Uptime: 4 9s minimum for paying customers for the core service (not necessarily the social features, but pull requests have to work).
More AI it is