Some time ago Jonathan Blow ranted about the horrible state of source code management and assets (for game developers) on his Twitter account. To demonstrate his point of view he linked to the following article: Unorthodocs: Abandon your DVCS and Return to Sanity.
My first contact with DVCS was during my bachelor studies when my group dropped our university's SVN server and switched over to the inevitable github.com. The handling of Git was nice and I really liked it since then.
As I read the mentioned article I realized that Git was the only DVCS I knew at that moment so I gathered information I could find.
- GitMinutes #07: Martin Geisler on Mercurial - really interesting. You should listen to GitMinutes - no matter which VCS you use (thank to @0xmf for pointing me towards the GitMinutes podcast).
- The Real Difference Between Mercurial and Git
- Git Koans (related to previous article).
- FLOSS Weekly 122 - podcast including an interview with Matt Mackall, project leader of Mercurial.
- Das SCM Mercurial - German podcast.
- Kallithea SCM - GPLv3-licensed (grml) Mercurial and Git SCM.
- Github Flow.
- A successful Git branching model - apparently for larger code bases and bigger teams.
Why do I like Mercurial?
- Conservative code changes (as I like my Unices).
- Backwards compatible for as long as the major version number is the same.
- Mainly written in Python (5% C for performace related code).
- Source and destination are consistent (unlike Git).
SCM unrelated link:
- Semantic Compression - interesting read for programmers.