I'm disappointed that this is an issue for some package management systems. 20 years ago I helped run a mirroring service, it's still running today. Distributions such as Debian have hundreds of mirrors. This is a solved problems, but we just decided to but everything in the hands of one for-profit company.
What I find funny and unexplainable is that this class of problem was solved decades ago with distribution mirrors. It's not really clear to me why, within the last decade or so, we collectively decided to centralize hosting on one specific cloud service whose downtime now affects builds across nearly every company.<p>What's perhaps even more surprising to me is that, after a repeated track history of severe and frequent Microsoft-Github outages in the last three years, it is <i>still</i> a hard dependency for so much of the modern software stack.
Oh dear, Last time this happened was 11 days ago when more than just packages went down. [0] Perhaps relying and going all in on GitHub doesn't seem to be good in the long run. Especially GitHub Actions.<p>This is where OpenAI is now feeling the effects of instability [1] on Azure since their recent outage. I expect them to also have issues like GitHub has every month.<p>[0] <a href="https://news.ycombinator.com/item?id=34843748" rel="nofollow">https://news.ycombinator.com/item?id=34843748</a><p>[1] <a href="https://news.ycombinator.com/item?id=34958375" rel="nofollow">https://news.ycombinator.com/item?id=34958375</a>
The "is" seems to be used confusingly here. This reads better as either:<p>* GitHub's Packages Service is down<p>* GitHub Packages are down