Hacker News Reader

Comment by maaaats | Hacker News Reader

But most people never use the distributed part of git, other than having the repo on their local computer.

Just being able to continue working and committing locally and pushing to Github when it comes back up is still a DVCS win over SVN. People may not use the distributed part of git to its fullest, but they do use it.

That is true. When working at a project at work which uses SVN, I luckily have IntelliJ's great stashing/changelist features, acting like a local branch.

Many of our projects are using SVN just because it's the easier one (at least until lately) to configure and set up locally. So that's a small win for SVN, and removes the issue of GitHub being down.

If you have a co-worker with full copy of repository, isn't it already somewhat distributed? Of course it is not all attached to network.

The real problem that we should be talking about is - Pull request based workflow many companies (including mine) have adopted. Which doesn't work when github goes offline.

I hear from lot of teams, they have switched to using github issues for project managment entirely, so as pull request and tickets can be "seamlessly" linked. That goes out of window as well.

After using Jira for a year (with Grasshopper), I can't imagine a company with more than a few developers maintaining everything with github issues. shudder

But yes, you are right. Being able to copy it from my neighbor is nice.

For us, GitHub issues > corporate intranet. Beyond that, JIRA just doesn't add enough to be truly worthwhile.

Sounds like they should learn.

Reply on news.ycombinator.com