4 ms·
I have significant experience with CSV, SVN, Perforce, Source Depot (Microsoft's internal Perforce fork), Team Foundation Server, Mercurial, and Git. Roughly in
by snprbob86 15y ago
I have significant experience with CSV, SVN, Perforce, Source Depot (Microsoft's internal Perforce fork), Team Foundation Server, Mercurial, and Git. Roughly in that order of exposure.
I safely say that TFS is easily the slowest, least scriptable, most confusing, obnoxious piece of crap software that I have ever had the displeasure of using. The Microsoft-internal hate for TFS was astonishing, but political pressures forced us to use "dogfood" it.
Personally, I used to keep all of my source code at Microsoft in a local Mercurial repository (this was before Git had decent Windows support). I only interacted with TFS when I absolutely had to.
- hyperrail 15y agoHow recent was your experience with TFS? It's been around for 6 years and shipped 3 versions, that should be enough time for it to be good enough for dogfood.
- snprbob86 15y agoYou'd think that right? But I left Microsoft in spring of 2010.
- sid0 15y agoOh man, I did the same when I was at Microsoft for a couple of months for an internship (although I had to interact with SD instead). Coming from hg I found SD to be pretty obnoxious. Thankfully my mentor was fine with it: "whatever works for you".
- cpeterso 15y ago> I have significant experience with CSV, SVN, Perforce, Source Depot (Microsoft's internal Perforce fork), Team Foundation Server, Mercurial, and Git. TFS is a worse source control system than CSV? That is bad! ;)
- snprbob86 15y agoHeh, whoops. I always transpose those two letters. I can't get that acronym right regardless of which one I'm trying to type! But yeah, I wouldn't be surprised if there was someone somewhere who had a pile of CSV-based shell scripts that outperformed TFS.