4 ms·

You would have made a valid point if git wasn't fully distributed. But it is. And every dev has full copy of the repository. This is only a temp DDoS situation

by toong 12y ago

You would have made a valid point if git wasn't fully distributed. But it is. And every dev has full copy of the repository. This is only a temp DDoS situation ? And you can host your code repository elsewhere. You can even use multiple remotes simultaneously. Not that it's convenient (that's why we use Github), but hell, you just create some ssh-accounts for your colleges and host the repository on your laptop ? Sorry, who was laughing and why ?

mikekchar 12y ago
It's a very good point. I had a slight inconvenience today because I was missing one commit on a branch that I wanted. But I could easily get it from my colleague. If my colleague wasn't available, then I've only missed one commit. It's not a massive issue to just redo the work. When I get access to the commit I'm missing I can even diff my changes against it and choose which one I like better. Even if Github went away completely, we wouldn't have that much of a problem. It is important to have systems that maintain a copy of old projects, though. It would be easy to think, "Oh it's in Github. I don't have to worry about it." But that's stupid, of course (not that it will stop people from doing it...)
dagw 12y ago
The real problem that I can see is not for developing, but all the build and deployment systems that are hard coded to pull in dependencies from github.
- toong 12y ago
  Fair point. But now you're not using Github for development. If your deploy process involves Github, you actually promoted it to be part of you production/operations infrastructure ? That's where the 'wise and mature tech person' comes into play, I guess ;-)
rlpb 12y ago
> You would have made a valid point if git wasn't fully distributed. But it is. Except for Issues and Pull Requests, which are essential to continuing ongoing development. Mailing lists are better distributed for this than Github.

by toong 12y ago

mikekchar 12y ago

It's a very good point. I had a slight inconvenience today because I was missing one commit on a branch that I wanted. But I could easily get it from my colleague. If my colleague wasn't available, then I've only missed one commit. It's not a massive issue to just redo the work. When I get access to the commit I'm missing I can even diff my changes against it and choose which one I like better. Even if Github went away completely, we wouldn't have that much of a problem. It is important to have systems that maintain a copy of old projects, though. It would be easy to think, "Oh it's in Github. I don't have to worry about it." But that's stupid, of course (not that it will stop people from doing it...)

dagw 12y ago

The real problem that I can see is not for developing, but all the build and deployment systems that are hard coded to pull in dependencies from github.

toong 12y ago
Fair point. But now you're not using Github for development. If your deploy process involves Github, you actually promoted it to be part of you production/operations infrastructure ? That's where the 'wise and mature tech person' comes into play, I guess ;-)

rlpb 12y ago

> You would have made a valid point if git wasn't fully distributed. But it is. Except for Issues and Pull Requests, which are essential to continuing ongoing development. Mailing lists are better distributed for this than Github.