分布式版本控制系统会继续存在吗？

Question

就我个人而言，我是SVN爱好者，但我开始成为围绕DVCS的热潮的牺牲品。

SVN是免费的，经过时间测试，DVCS是新的SVN吗？

我也在寻找哪种DVCS服务器会胜出GIT或Mercurial？

Answer 1

你可以看看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.

​

编辑

• 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

​

编辑

• Disadvantages

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

​

然而，归根结底，我相信这将归结为公司使用什么。看看COBOL，它仍然在很多地方被使用，即使它已经被教授了那么多。已经实现了这一点的公司很可能会保留现有的东西，而不是改变一切来适应新的炒作。国际海事组织。

Answer 2

据我所知，每个分布式版本控制系统都是免费的。分布式系统提供了如此多的好处，我认为真正的问题是传统系统是否会生存下来。我对此的回答是否定的。

Answer 3

谁会赢，Git还是Mercurial？双方都将是“赢家”。

• 它们在使用上非常相似。学习Git或Mercurial的人可以很容易地从一个切换到另一个，只需学习如何以不同的方式表达一些命令。(最大的区别在于高级用法)。
• 它们是可以互操作的。你可以在Mercurial和Git仓库之间推送数据，而不会丢失information.
• There's，没有真正令人信服的理由从Git切换到Mercurial，反之亦然。Google为"git dvcs“返回494k个结果，为"mercurial dvcs”返回342k个结果。Bzr有173k，Darcs有51k。