Lots of people have been liking Git over the last few years. Git is the SCM system created by Linus Torvalds, aka Mr. Linux. But not everyone likes Git and they’re starting to say so.
One of the big knocks against Git is its complexity for the user. The information model, command line syntax, and multiple steps required for basic operations are fine with some people but frustrate others. Steveko’s Blog has a great rundown of many of the difficulties with Git. It’s a good read whether or not you’re a Git fan.
In other Git news, GitHub was recently hacked. There’s a lot of code up there, and now people are worried about the security of their work.
At this point I should warn you that a shameless plug is coming. But since I have no shame…
Rational Team Concert’s SCM systems is philosophically similar to Git’s, but doesn’t load up the user with a lot of extra complexity. Git’s patches are much like RTC’s change sets. Both systems have workspace areas locally and remotely, with separate actions required to move code from your workspace to a common delivery area. There are lots of terminology differences, but many similar perspectives on how to get the work done.
At the same time, RTC manages to keep the code/check-in/deliver cycle reasonably simple. Check-ins can even be done automatically since the code stays in your own workspace (on the server). And RTC provides licenses for small teams (up to 10 developers) when you download the product. At the same time, RTC includes process enactment, project planning, change management, and other goodies.
IBM has also started JazzHub, an SCM hosting environment for academic projects based on RTC. You might want to check this out if you’re part of the academic community.
So if you want a Git-like SCM model plus a lot of other integrated functionality, check out RTC.
And now I’m putting my Shame Glasses back on.