Created
June 20, 2011 01:03
-
-
Save jakcharlton/1034970 to your computer and use it in GitHub Desktop.
Pros and Cos of TFS and Git
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| TFS | |
| Pros | |
| • Familiar to current team | |
| • Has a UI tool within Visual Studio | |
| • Close tie in to Work Items | |
| Cons | |
| • Slow to pull, check in and branch | |
| • Merge conflicts are frequent | |
| • Encourages infrequent check in due to merge conflicts and slow performance | |
| • Branching frequently leads to time consuming conflicts | |
| • Central repository requires connection to safely work (disconnected model is unreliable) | |
| • Requires Visual Studio | |
| • Server managed workspaces cause pain when straying from the happy path | |
| Git | |
| Pros | |
| • Distributed source control, no central repository to depend upon | |
| • Low friction branching | |
| • Low friction merging encouraging frequent check in | |
| • Ability to cherry pick commits, for example to hotfix | |
| • All actions are near instant | |
| • Modern tools are far more adept at integrating with Git than they are with TFS | |
| Cons | |
| • Small learning curve for people familiar with TFS | |
| • No “integrated experience”, other tools required for issue management, CI, etc | |
| • Hosting your own Git server is not a totally friction free setup experience | |
| • Risk of taking bad TFS habits to Git |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
TFS Con: you need to make sure the central server is backed up
Git Pro: You can have local version of GitHub: http://fi.github.com/