24 ms·

It gives me the chuckles every time I hear Github or Gitlab goes down. Because one of the main points of Git was to provide a "distributed" version control sys

It gives me the chuckles every time I hear Github or Gitlab goes down. Because one of the main points of Git was to provide a "distributed" version control system. Meaning that you are probably using it wrong if your entire company completely halts to a stop just because Github/Gitlab/Bitbucket are down. Maybe what we need is a service that automatically consolidates them for you so your repos are always online?

NoodleIncident 7y ago
I don't really understand your point. Everyone still has their copy of the repo, and they can keep working on their code. That's the distributed part. It's still important to be able to share that code, trigger builds and tests, etc.
bob33212 7y ago
These organizations are not distributed hiveminds. Someone in authority has to approve the code change, and someone above that person has to verify that the code is being approved appropriately, and someone above that person has to monitor everything below them. If you are working on a solo project it doesn't matter if the remote repo goes down, just push to another Linux server
count 7y ago
Do you think Github is nothing more than a 'central git' repo? Have you even used the site in the last few years?
- dang 7y ago
  > Have you even used the site That's a variant of "did you even read the article", which the guidelines ask you not to do (see https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html). That's partly because it's a putdown, but mostly because there's no information in it. Readers who know less than you do are here to learn, so a better version of this comment would share some of what you know.
  - count 7y ago
    I disagree, and it was definitely not intended to be a put down. It's a question, because it appears the OP was speaking of GitHub as it was, not as it is. I don't question their intelligence or ability to read. But whatever.
michaelmior 7y ago
> a service that automatically consolidates them for you What is the "them" you're referring to? Perhaps you're talking about consolidating multiple hosting services? This seems dangerous. What happens if Susan can access GitHub but not Gitlab and the reverse for Thiago. Susan pushes updates to GitHub, Thiago pushes updates to Gitlab and now you have to figure out how to reconcile the too. Of course you have a similar problem if both commit different changes locally, but in that case it's generally agreed upon that the hosting service holds the version of record and that developers should reconcile changes against this.

NoodleIncident 7y ago

I don't really understand your point. Everyone still has their copy of the repo, and they can keep working on their code. That's the distributed part. It's still important to be able to share that code, trigger builds and tests, etc.

bob33212 7y ago

These organizations are not distributed hiveminds. Someone in authority has to approve the code change, and someone above that person has to verify that the code is being approved appropriately, and someone above that person has to monitor everything below them. If you are working on a solo project it doesn't matter if the remote repo goes down, just push to another Linux server

count 7y ago

Do you think Github is nothing more than a 'central git' repo? Have you even used the site in the last few years?

dang 7y ago
> Have you even used the site That's a variant of "did you even read the article", which the guidelines ask you not to do (see https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html). That's partly because it's a putdown, but mostly because there's no information in it. Readers who know less than you do are here to learn, so a better version of this comment would share some of what you know.
- count 7y ago
  I disagree, and it was definitely not intended to be a put down. It's a question, because it appears the OP was speaking of GitHub as it was, not as it is. I don't question their intelligence or ability to read. But whatever.

michaelmior 7y ago

> a service that automatically consolidates them for you What is the "them" you're referring to? Perhaps you're talking about consolidating multiple hosting services? This seems dangerous. What happens if Susan can access GitHub but not Gitlab and the reverse for Thiago. Susan pushes updates to GitHub, Thiago pushes updates to Gitlab and now you have to figure out how to reconcile the too. Of course you have a similar problem if both commit different changes locally, but in that case it's generally agreed upon that the hosting service holds the version of record and that developers should reconcile changes against this.