News for hackers. Stuff that matters.
Re:GitHub had connectivity problems by ilghiro on Tuesday August 25, 2015 @07:20AM (#10115661)
Yeh it's definitely preferable to have one of the two developers your small startup can probably afford spending a good portion of their time rolling out, securing and maintaining your own infrastructure
Re:GitHub had connectivity problems by bad_user on Tuesday August 25, 2015 @08:06AM (#10115830)
GitHub is not meant for distributing dependencies. Maven Central on the other hand is, the difference being that it is mirrored and if repo1.maven.org goes down, it's not a big deal and your project can still be built and deployed.
Re:GitHub had connectivity problems by wereHamster on Tuesday August 25, 2015 @08:38AM (#10115987)
.. until they become a target of a DDoS.

Also, if GitHub is down you can still fetch your dependencies from somewhere else.

Re:GitHub had connectivity problems by JumpJumpJump on Tuesday August 25, 2015 @09:03AM (#10116116)
You have not understood the concept of 'mirrored'.
Re:GitHub had connectivity problems by chopman on Tuesday August 25, 2015 @09:51AM (#10116432)
Well I guess all mirrors could get targeted. Also, what stops github from getting mirrors themselves?
Re:GitHub had connectivity problems by biggestbob on Tuesday August 25, 2015 @07:32AM (#10115711)
Yeh cos those are two only two options available. Good thinking.
Re:GitHub had connectivity problems by satanrepents on Tuesday August 25, 2015 @09:54AM (#10116452)
An internal GitLab install isn't that time consuming to maintain. Also: dat false dichotomy.
Re:GitHub had connectivity problems by modarts on Tuesday August 25, 2015 @12:46PM (#10117784)
False dilemma much? Private versions of most dependency repos exist (npm, maven, etc)