Fine. Git is Awesome.
justin.harmonize.fm
justin.harmonize.fm
Git is Awesome because it is a Mercurial with easily editable commit history, "better" local branches and the killing feature -- git-svn.
I know that support can be hacky at best in a DVCS but often, especially in the common "semi-centralized" workflow, that's good enough. Don't underestimate the communication benefits of being able to talk about specific revisions in chronological context, in plain english. "That was fixed in 982" is much easier to parse and congest for a human than "That was fixed in d934c8" or "That was fixed on last Tuesday".
Why not do something to improve yourself, like learn C or Lisp, or port some sortware?
If you seriously think those are in opposition, you either need more experience with version control (preferably a modern one) or more experience with coding in a real environment with many people. Possibly both.
There really isn't any two ways about that. The only two ways you can think version control is worthless is if you've only used worthless version control (Hi, Visual Source Safe!) or you're caught on the wrong end of a Blub paradox.
I have a guy at work who thinks version control is beneath him, too. I say him and his twenty distinct-and-slightly-different versions of critical scripts that require huge maintenance (often incompletely done) for every trivial change are wrong, and I end up paying the price.
I would never suggest undertaking a major coding project without some form of version control. However, it's a tool used to improve your work; going nuts over git (which seems to be the fashionable thing these days) is like an artist raving over how great his paintbrushes are and making special little boxes for them, or a carpenter who won't stop talking about his hammer when he's supposed to be roofing your house.
However, DVCS systems are better than the previous state-of-the-art, by enough to be excited about. Not fanboyish about, but certainly excited about.
Now, though, I couldn't agree with this article more!
Seriously, though, git-svn is very low on user interface, so you should be able to take the standard git plugin:
http://git.or.cz/gitwiki/EclipsePlugin
and use that for most of your work. When you want to get changes from svn, or commit changes to svn, just open up an xterm and type "git svn rebase" or "git svn dcommit". You may even be able to get Eclipse to run an arbitrary shell command for you, if so, you're set.
Also, my work is gasp enterprise java duck. Eclipse integration with JUnit, Ivy, svn, ant, etc etc, saves me lots of time. My cover is blown :(
There is a pattern here: embrace the legacy without giving up any advantages of the modern.