3 ms·

This may be sacrilege on here, but at my previous job I really enjoyed TFS. It's been awhile but the workflow felt a little more intuitive than git. And some of

This may be sacrilege on here, but at my previous job I really enjoyed TFS. It's been awhile but the workflow felt a little more intuitive than git. And some of the merging features were nicer.

maxxxxx 9y ago
I used to work with TFS but after working with git I can't stand it anymore. But it shows that people have different tastes.
- kylemuir 9y ago
  Strongly echo this sentiment. Last time I used TFS was probably in 2011 so things might have changed significantly since then but off the top of my head things I use to hate but now don't need to worry about since using git over TFS: - Offline? Looks like you'll have to wait to make that change or any other change for that matter since you can't check out files if you're offline. When doing remote work this use to do my head in. - TFS On Premise putting readonly locks on every file you have. Why? Great question. Made writing build scripts and their ilk much harder to accomplish. - Want to make a branch? That'll be an entire copy of the source code times however many branches you want
  - maxxxxx 9y ago
    Add to that detection of new files or deletions outside of visual studio. This is so easy in git and a real problem in TFS.
GordonS 9y ago
I've worked with TFS and SVN for more than 10 years, and Git for maybe 5. I find TFS the slowest of the lot, by quite a large margin.
Chromozon 9y ago
TFS is great if everything in your codebase is a Visual Studio project. If you are trying to use it for other things, there are better version control systems out there. My ranking is Perforce > Git > TFS > SVN. I haven't used Mercurial. I like Perforce the best because of its clean UI, its explicit checkout mechanism (all files are read-only by default, and you have to check out anything before you can edit), the integration tool GUI, and the ability to cloud-save work without submitting it. TFS is nice because it has built-in code review, but the UI isn't nearly as clean as Perforce.

This may be sacrilege on here, but at my previous job I really enjoyed TFS. It's been awhile but the workflow felt a little more intuitive than git. And some of the merging features were nicer.

maxxxxx 9y ago

I used to work with TFS but after working with git I can't stand it anymore. But it shows that people have different tastes.

kylemuir 9y ago
Strongly echo this sentiment. Last time I used TFS was probably in 2011 so things might have changed significantly since then but off the top of my head things I use to hate but now don't need to worry about since using git over TFS: - Offline? Looks like you'll have to wait to make that change or any other change for that matter since you can't check out files if you're offline. When doing remote work this use to do my head in. - TFS On Premise putting readonly locks on every file you have. Why? Great question. Made writing build scripts and their ilk much harder to accomplish. - Want to make a branch? That'll be an entire copy of the source code times however many branches you want
- maxxxxx 9y ago
  Add to that detection of new files or deletions outside of visual studio. This is so easy in git and a real problem in TFS.

GordonS 9y ago

I've worked with TFS and SVN for more than 10 years, and Git for maybe 5. I find TFS the slowest of the lot, by quite a large margin.

Chromozon 9y ago

TFS is great if everything in your codebase is a Visual Studio project. If you are trying to use it for other things, there are better version control systems out there. My ranking is Perforce > Git > TFS > SVN. I haven't used Mercurial. I like Perforce the best because of its clean UI, its explicit checkout mechanism (all files are read-only by default, and you have to check out anything before you can edit), the integration tool GUI, and the ability to cloud-save work without submitting it. TFS is nice because it has built-in code review, but the UI isn't nearly as clean as Perforce.