Beanstalk vs. Mercurial

For business or personal applications, where you wish your code to remain private and/or proprietary, Beanstalk could be a good fit. If you are also interested in beginning to automate with relative ease, their tools can be a great help. Code reviews can also be a key factor in the decision, as they provide a good framework for accountability.

Incentivized

If you generally think that to develop software you have to choose one repository, then in my opinion you have to choose between Mercurial and Git, there is not other solution. Mercurial also has a good merge tool which i can recommend. This gives you the flexibility to push just the "part of the feature", and is much better suited in the case where the "part of feature" and some other "part of the feature" both contain changes to the same file.

Incentivized

• Automation
• Code Review
• Support

Incentivized

• Branch
• Distributed architecture
• Stable
• Platform independent

Incentivized

• Interface is not always intuitive, some areas are easier than others to navigate.
• Price plans are a little odd. However, they do seem to be flexible if a plan does not quite fit your needs.

Incentivized

• Integration with visual studio
• More integrated tools
• When I install Mercurial I always have to do a hard restart of my computer.

Incentivized

If you are creating open source applications, there is almost no reason not to use GitHub. If you do need private repositories (for proprietary or private, business or personal use), Bitbucket could be an excellent solution. Beanstalk's main advantages lie in the support (which is excellent), deployment tools, and code review features.

Incentivized

When we chose Mercurial it was more popular from perspectives than Git and we have too many problems with the Microsoft team foundation solution. We also want to move from a centralized version of source control to a distributed one. We also were working more and more via the Internet with our source control so distributed version was only solution.

Incentivized

• Increased automation => better accuracy and efficiency of maintenance/launches
• Better insights into ongoing work and past modifications to code => lower chance of error and more efficient troubleshooting

Incentivized

• Improve time in merging
• Branching enables us to keep separate version per customer
• Good tool for programmers is sometimes a reason to stay

Incentivized