We looked at few solutions at our startup and we decided to go with git instead of Hg after we launch (we'll use svn until then). I actually liked both and liked Hg a bit more due to its simplicity but since the Rails world has adopted git and everyone's distributing code using git and github, the decision was basically made for us.
We're in the same boat. We've been using Subversion, but will switch to git once our tools support it (we eat our own dog food, and Subversion is the only revision control system our products support right now). The determining factor for us was similar, as well...the Perl core developers appear to be moving to git for all Perl development. We're a mostly Perl shop, so we'll go where Larry and Co. goes. It just insures that the tool-chain for working with our codebase with git will be really solid, if the majority of Perl developers are also using it.
You know about the git svn bridge, right? It comes right in the standard git distribution, works intuitively and easily, and is the only thing keeping me sane as I work on two projects managed in Subversion. Basically, I use git in my development environment, with all the slick branching, merging, and great performance. Then I push code out to Subversion, and it all just works.
