On Thu, Nov 4, 2010 at 6:26 AM, Joseph Cooney <joseph.coo...@gmail.com> wrote: > I've used TFS on and off since about 2006 (mostly because I was working at > MS, as they are fond of TFS), but haven't used TFS 2010. It's biggest > strength IMO is integration - requirements, work items, bugs, builds, source > code and project documentation all from within Visual Studio. It's biggest > weakness is that it's not a distributed version control system (git, > mercurial).
Without sounding too argumentative; exactly why should I care that version control is "distributed"? The stated arguments seem to be that you don't need to be online to do commits, or that there is a local history, or some other such things. I really just don't ever find the need for anything like that; am I doing something significantly different to everyone else? I mean, I've glanced over this: http://betterexplained.com/articles/intro-to-distributed-version-control-illustrated/ and it seems none of the benefits are really appropriate in a 'typical' environment. I guess what I'm asking is - is anyone, working in an office or alone, getting specific benefits from git or whatever, that come *purely* from it being significantly different from SVN, and exactly what are they? > If you're just going to use it as a revision control system > you're missing out on 80-90% of what TFS has to offer (and thus it might not > be worth it). TFS 2010 is a major update to the product (v2 really, since > 2008 was really a v1.1) so I'm doubtless overlooking some cool features > there 'cause I haven't used it. > Joseph > > w: http://jcooney.net > t: @josephcooney -- silky http://dnoondt.wordpress.com/ "Every morning when I wake up, I experience an exquisite joy — the joy of being this signature."
