Source Control

[Taxious]

The new job is using TFS, I've only had experience with SVN until now, and Git seems to be trending through the industry. So far my first impression of TFS is that it's extremely slow and over complicated. I realize TFS is meant to be more than just a source control tool, but in regards to using it for source control, it seems inflated. I don't like that editing a file automatically checks it out and locks it to you. It's cool that it integrates with Visual Studio but it seems to clog the IDE up more than working with it. And shelving a change before actually committing it is a cool idea, but it locks up my VS and has just been a hassle so far.

What do y'all use?

[Freecare Spiritwise]

You guys talked me into SVN, and we've been using it a couple years. I personally like it, and it's fast. Right now it's probably perfect for us since I wouldn't trust my overseas team to quickly pick up something like Git. They could barely get through Source Safe.

Git seems cool, but I question why most people would need it over something like SVN. But again, I haven't used it. I could see for a large team that's geographically separated to use distributed version control, but it seems like a lot of overhead for most teams.

I noticed that Google offers free SVN hosting, which turns your project into defacto open source. But I might use it for my blog. And I'll probably hunker down and learn Git just to pad my resume. But again, in my experience, most programmers struggle with basic version control concepts.

[Taxious]

I miss my SVN! I keep thinking that I'll learn some cool trick with TFS that makes me fall in love with it, but so far the more I use it, the more I dislike it. It boggles my mind that we are paying for TFS when SVN is faster, better, and... free!

But again, in my experience, most programmers struggle with basic version control concepts.

Oh? I've ran into some issues with tree conflicts that have given my team grief but it seems like everyone I've worked with picks it up rather quickly.

[Freecare Spiritwise]

Oh? I've ran into some issues with tree conflicts that have given my team grief but it seems like everyone I've worked with picks it up rather quickly.

I just meant as a general statement that over the years it seems like people are inherently scared of version control and never do much with it other than the bare minimum the team expects from them. There's usually not a lot of folks in the organization that have very much mastery over it. It's an obstacle, a necessary evil, not some cool powerful thing that can make your team work better. I've seen a lot of fumbling and not much true understanding. But I've been out of touch the last few years. Maybe expectations have gone up.

[Minute]

I like Git. Eclipse makes using it super easy.

[Ddrak]

Massive fan of git now (although hg and bzr are probably just as good). Significantly faster than subversion, handles branching way better (team currently working on 164 branches concurrently), and being able to merge from wherever you want without worrying too much is pretty awesome.

Of course, you do have to plan what you're doing and there's a small learning curve about what's a good idea and what isn't. TortoiseGit smooths most things over.

Still, svn is pretty good and if it's working for you then don't change anything!

Dd