How Do You Control Your Source Code?

[eluser]jedd[/eluser]
Sure, I absolutely agree that if you're going to work for a shop that uses a certain type of software, then you'd learn that software. So if you were going to work for Google, you'd learn Perforce. If you were heading into a Microsoft-based shop you'd shoot yourself in preference to having to deal with SourceSafe or TFS. But yes, I understand the implication - because lots of people use subversion, there's a commercial imperative to understand it. Happily nothing in the original post suggests the existence such an imperative.

I think your learning curve expectations might be based on experiences with earlier versions of git. By all accounts it used to be pretty horrendous. I gather it's now considered to be comparable, in terms of command complexity and (ease of) feature accessibility.

For a two-machine setup, with little chance of collaboration with other humans, where high performance and a cheap branching mechanism are the two biggest selling points, it'd be a tough call to pick a server-centric, slower-performance system.

Curiously, I recently found the site [url="http://whygitisbetterthanx.com"]Why git is Better than X?[/url] which lists [url="www.github.com"]github[/url] as being one of the biggest selling points for git. I hadn't really thought about that before, but github is where I first got the warm and fuzzies about git. Maybe there is a subversionhub out there (googling for it takes me to a London S&M club .. which happily answers the question 'What will I do tonight?')