61–70 of 253 posts
Earlier quoted context omitted.
If only you were using a decentralized VCS, you wouldn't have this single point of failure…
but github is honestly so nice. I'll admit in a very subjective way. whats your favorite decentralized vcs?
I would love to see a chart of traffic to other sites when GitHub goes down. My bet is that HackerNews and Twitter both get significant spikes from all those bored developers.
> bored developers Bored? Git's a distributed version control system, so no excuses. Get back to work! But in all seriousness I kind of wish GitHub provided a way to mirror things like issues and PRs so you never have to be fully reliant on one service. Not being able to read these really does make it impossible to get work done offline.
Github is not a open source company, it is not really even a supporter of free software IMO they are a danger to free software for this very reason. They are following the old school Microsoft model of Embrace and Extend... I am waiting to see if they can extinguish,
I would love to see a chart of traffic to other sites when GitHub goes down. My bet is that HackerNews and Twitter both get significant spikes from all those bored developers.
> bored developers Bored? Git's a distributed version control system, so no excuses. Get back to work! But in all seriousness I kind of wish GitHub provided a way to mirror things like issues and PRs so you never have to be fully reliant on one service. Not being able to read these really does make it impossible to get work done offline.
How many more can we expect before they develop appreciation for testing _before_ they push to prod?
Newly introduced errors in site code are only one of many sources of failure for a site like GitHub, and probably a fairly rare one.
Earlier quoted context omitted.
If only you were using a decentralized VCS, you wouldn't have this single point of failure…
The problem isn't the VCS part so much as all the code review/project management features of Github. I seem to remember there was a decentralized VCS which included issue tracking besides commits, but it never was mainstream.
Earlier quoted context omitted.
If only you were using a decentralized VCS, you wouldn't have this single point of failure…
The problem isn't the VCS part so much as all the code review/project management features of Github. I seem to remember there was a decentralized VCS which included issue tracking besides commits, but it never was mainstream.
What was happening to Github for a week or so in late June - early July? I see "The status is still red at the beginning of the day" for a whole week. https://status.github.com/messages/2017-07-03