Will Distributed Version Control Systems survive? [closed]_问答_开发者

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by 开发者_开发知识库facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance. Closed 12 years ago.

I am personally a SVN lover, but am starting to fall prey to the buzz that is surrounding DVCS.

SVN is free, and time tested, is DVCS the new SVN?

I am also looking for which DVCS server will win out GIT or Mercurial?

Every distributed version control system that I know of is also free. Distributed systems offer so many benefits, that I think the real question is whether traditional systems will survive. My answer to that is no.

Which will win, Git or Mercurial? Both will "win".

They are very similar in use. People who learn Git or Mercurial can easily switch from one to the other, only having to learn how to word some commands differently. (The biggest differences lie in advanced usage).
They are interoperable. You can push data between Mercurial and Git repositories without losing information.
There's no real compelling reason to switch from Git to Mercurial or vice versa.
Neither is much more popular than the other. Google returns 494k results for "git dvcs", and 342k results for "mercurial dvcs". Bzr has 173k and Darcs has 51k.

Well you can look at the advantage and disadvantages on wiki

Differences
- There may be many "central" repositories.
- Code from disparate repositories are merged based on a web of trust, i.e., historical merit or quality of changes.
- Lieutenants are project members who have the power to dynamically decide which branches to merge.
- Network is not involved in most operations.
- A separate set of "sync" operations are available for committing or receiving changes with remote repositories.

[edit]

Advantages
- Allows users to work productively even when not connected to a network
- Makes most operations much faster since no network is involved
- Allows participation in projects without requiring permissions from project authorities, and thus arguably better fosters culture of meritocracy[citation needed] instead of requiring "committer" status
- Allows private work, so you can use your revision control system even for early drafts you don't want to publish
- Avoids relying on a single physical machine. A server disk crash is a non-event with distributed revision control
- Still permits centralized control of the "release version" of the project

[edit]

Disadvantages
- Concepts of DVCSs are more difficult for developers to grasp as they are required to know more about infrastructure.

however in the end I believe what it would come down to is what companies use what. Look at COBOL, it is still used in a lot of places even though it's even taught that much anymore. Companies that already have this implemented will most likely stay with what they have instead of changing everything to accommodate the new hype. IMO.

Distributed Source Control is great, however it really depends on what kind of project you're working on. Most companies need a centralized repository as a point that everyone can reference. So when you are looking at tools like GIT or Mercurial..it isn't the "Distributed" that is the important sell for a big company (although there are niceties because of this, this is not the most important thing). The beauty of them is the fact that they make merging branches much easier. This causes you to be able to branch more often and effectively, and commit at more intermediate steps than you would on a "centralized" system. Yes, these are largely due to the fact that they are designed in a distributed model, but not entirely so. I personally love GIT...but I use it with a centralized "repository" for work because it's what makes sense for the business.

As far as being free, that's not really an issue. Most (if not all) Distributed source control systems are free. Only time will tell who "wins out" but if I had to place my bet, I'd say neither. There are dozens of SCM out there that all fail equally, and thousands of companies use each of them.

I don't think we'll see medium or large companies move away from centralized systems any time soon. Large companies care about centralization and control. They have governance and compliance issues to deal with and they need centralization to manage that. So I think you'll continue to see centralized systems in the enterprise.

At the same time, DVCS will most likely dominate the open source ecosystem. We're already seeing this with the recent rise in popularity of Git and Microsoft supporting Mercurial on codeplex.

Personally I would love to see a combination. I think a centralized server for tracking "official" repositories would help in an enterprise environment, but a distributed working copy allowing cheap branching and merging for individual developers would be very useful.

I blogged about this the other day specifically in regards to Subversion. I'm not sure how likely it is that we'll see anything like this come from the SVN team, but I think it could be really powerful.

http://www.sublimesvn.com/blog/2010/03/subversion-vision-conference-distributed-subversion-unlikel/