3 ms·

The very fact that git is distributed means that if github was down for a week your development shouldn't suffer, just become more annoying maybe, but you can e

The very fact that git is distributed means that if github was down for a week your development shouldn't suffer, just become more annoying maybe, but you can easily so without GitHub I'd you know the ABC of how git works. Your theory doesn't hold when comparing github with infrastructure everybody uses but few people know about, just because its used by many people that write programs that are used by many other users doesn't mean it's an infrastructure like an Internet backbone.

derefr 13y ago
> your development shouldn't suffer, just become more annoying maybe Right, that's why I wrote "has been delayed a bit", not "has been delayed indefinitely." If you run a distributed OSS project, where your main point of contact with your collaborators is through Github--and your workflow relies on using Github's collaboration features (its wiki and issue tracking, its pull requests, etc.) then Github going down can greatly impede (though not halt) that workflow. (In fact, I might say that if your workflow doesn't rely on the collaboration features, you're not really "using" Github--you're just using git, and syncing with Github, like any project which has a Subversion repo with a Github mirror.) A more major problem with Github going down, though, would be needing to pull an update from a third-party library to fix a bug, when that library's canonical repo is stored on Github. (A problem with any centralzied repo host, really.) If you have any git:// URL dependencies in your Gemfile, or you use Bower at all, you might have a problem deploying your updates...